You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I noticed that some packages from the asset-store frequently use special characters in there BP variable names, which all get converted to "_" or are ignored completely.
Real rotation_ : 0.0
Real rotation_ : 0.0
Boolean forward? : false
Boolean forward? : false
Boolean forward? : false
than we get this error:
A variable with the name 'rotation_' has already been created and is available in this scope and duplicate/shadowed variable names are not allowed.
Choose a different parameter name.
Expected behavior
While i can work around this in my own code, its quite hard/time consuming to fix those errors for asset-store stuff.
So maybe its a better idea to convert special characters to some ascii/hex representation?
Something like:
ascii
Real rotation_62 : 0.0
Real rotation_60 : 0.0
or Hex
Real rotation076 : 0.0
Real rotation074 : 0.0
This way each special character gets encoded to a compatible variable name, without creating duplicates.
The text was updated successfully, but these errors were encountered:
Friday Nov 15, 2019 at 15:49 GMT
Originally opened as https://github.com/SkookumScript/SkookumScript-Plugin/issues/18
UE4 Version
Binary 4.23.1
SkookumScript Version
4.23.1-9631420
Describe the bug
I noticed that some packages from the asset-store frequently use special characters in there BP variable names, which all get converted to "_" or are ignored completely.
results in sk
than we get this error:
Expected behavior
While i can work around this in my own code, its quite hard/time consuming to fix those errors for asset-store stuff.
So maybe its a better idea to convert special characters to some ascii/hex representation?
Something like:
ascii
or Hex
This way each special character gets encoded to a compatible variable name, without creating duplicates.
The text was updated successfully, but these errors were encountered: