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
Its worth noting that IF the .pattern and .set files could be forced into ASCII XML then:
external editing/generation of files would be easier,
transferring files between people would be easier because they could be cut and pasted. At the moment a binary transfer mechanism is essential and difficult.
For example, no forum swaps are possible.
Its also probable that forcing ASCII XML could eliminate a number of other problems (e.g. multi-line notifications).
Neon22
changed the title
indicators not interpreting <cr> on load
indicators not interpreting CarriageReturn/LineFeed on load
Jan 18, 2020
If an indicator is saved with a CarriageReturn/LineFeed embedded in it appears like this in the .pattern xml file:
However on reload the carriage return is being ignored on reading and the indicator shows as a single line of text.
Note the character at the end of the line is a LineFeed. This is the same as every other line. so no CarriageReturn is actually in file.
Not sure if correct solution is in encoding to file, or in reading from file.
The text was updated successfully, but these errors were encountered: