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
I would like to be able to use leading spaces in my SLEIGH token definitions.
I have several string fields I concatenate using the "^" operator to form a mnemonic name.
If any of these fields are defined using leading spaces, they are automatically trimmed off.
Is there some way to escape out the leading spaces so they are preserved when the processor definition is compiled and used?
I hate to resort to patching code or using another delimiter like a period or underscore where a space is called for.
The text was updated successfully, but these errors were encountered:
I would like to be able to use leading spaces in my SLEIGH token definitions.
I have several string fields I concatenate using the "^" operator to form a mnemonic name.
If any of these fields are defined using leading spaces, they are automatically trimmed off.
Is there some way to escape out the leading spaces so they are preserved when the processor definition is compiled and used?
I hate to resort to patching code or using another delimiter like a period or underscore where a space is called for.
The text was updated successfully, but these errors were encountered: