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
Starting a bar with a rest directly after a symbol-less \section tag causes the r in the rest to be parsed as the section name, as the \section tag reads up to two "names" after it. Although this is the "expected" behavior from the parser, it leads to some confusion when learning the language.
This...
1.3.4*4 |
\section Verse
r.1 | 2.3.4*4 |
...causes this to be rendered:
My current workaround is to start the bar with a duration range instead:
1.3.4*4 |
\section Verse
:1 r | 2.3.4*4 |
Expected Behavior
The expected behavior from a new user of alphaTex would be for the r to be parsed as a rest in the example from above.
My suggested solution at this stage would be to disallow section names to be r, as it seems very unlikely for someone to legitimately use that. Fixing the "bug" and the confusion it brings is probably worth it. However, there are probably even better solutions to this problem.
Steps To Reproduce
See above
Link to jsFiddle, CodePen, Project
No response
Found in Version
1.2
Platform
Web
Environment
-**OS**: Windows 10
-**Browser**: Chromium 96
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Current Behavior
Starting a bar with a rest directly after a symbol-less
\section
tag causes ther
in the rest to be parsed as the section name, as the\section
tag reads up to two "names" after it. Although this is the "expected" behavior from the parser, it leads to some confusion when learning the language.This...
...causes this to be rendered:
My current workaround is to start the bar with a duration range instead:
Expected Behavior
The expected behavior from a new user of alphaTex would be for the
r
to be parsed as a rest in the example from above.My suggested solution at this stage would be to disallow section names to be
r
, as it seems very unlikely for someone to legitimately use that. Fixing the "bug" and the confusion it brings is probably worth it. However, there are probably even better solutions to this problem.Steps To Reproduce
See above
Link to jsFiddle, CodePen, Project
No response
Found in Version
1.2
Platform
Web
Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: