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
This issue applies to syllables that have the following characteristics:
The syllable contains only one neume;
That neume contains more than one neume component.
If you use the syllable selector and try to ungroup the syllable, nothing will happen, because Neon knows that you can't have more than one syllable per neume. So if you want to split that syllable, you have to first split the neume, then the syllable. This makes sense! My issue is with the notification: when you try to split a syllable without splitting its neume first, Neon gives you a green "Ungrouping Success" notification. This is confusing, because nothing happened, and unless the user is savvy, they won't know why. Demo:
Syllable.ungroup.notif.mov
My request would be to have a similar notification to when a syllable is toggled--something like "this syllable only has one neume; please ungroup the neume first." Would that make sense?
The text was updated successfully, but these errors were encountered:
This issue applies to syllables that have the following characteristics:
If you use the syllable selector and try to ungroup the syllable, nothing will happen, because Neon knows that you can't have more than one syllable per neume. So if you want to split that syllable, you have to first split the neume, then the syllable. This makes sense! My issue is with the notification: when you try to split a syllable without splitting its neume first, Neon gives you a green "Ungrouping Success" notification. This is confusing, because nothing happened, and unless the user is savvy, they won't know why. Demo:
Syllable.ungroup.notif.mov
My request would be to have a similar notification to when a syllable is toggled--something like "this syllable only has one neume; please ungroup the neume first." Would that make sense?
The text was updated successfully, but these errors were encountered: