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
The issue happens when the screen width is small (e.g. 300px, which is common for a mobile phone). For example, in the second line of the following screenshot, the grace note has overlapping issue; the third line doesn't have any display issue while having the same amount of notes.
When there's enough width, the overlapping issue won't occur.
This is the expected behavior. If there is simply not enough space for the notes to be placed, there must be overlaps. For each note a minimum size is calculated it requires. This size then influences the general spacing in the bar according to the time they are played (in a more-or less logarithmic scale). According to this notes are then placed. Grace notes are treated special: they are "sticking" to the next note following them.
There is always room for improvement (especially with grace notes) but I prefer not to touch this area currently unless it is really a misbehavior. In this case we could try adding a mechanism which would prefer a correct time position but rather avoid collisions. Not a straight forward thing.
For such small sizes I would recommend to switch to horizontal layouts or reduce the scale dynamically.
Is there an existing issue for this?
Current Behavior
The grace note is unnecessarily overlapping with the previous note, though the bar still has room to display the notes properly.
I found a similar issue (#1094), but seems the bug persists after the fix.
Expected Behavior
The grace note shouldn't overlap with the previous note.
Steps To Reproduce
It can be reproduced by uploading the tab to the demo player on alphatab.net
Please find attached the example gp file for reference.
grace-note.gp.zip
Link to jsFiddle, CodePen, Project
No response
Found in Version
1.3-alpha
Platform
Web
Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: