-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error thrown if next master doesn't contain current glyph #8
Comments
Going to a basic glyph that all masters have would lead to frustration (for me). FWIW, I don’t get a traceback, but hit a dead end when I try going to the next master – I can go backward again, but no longer forward (using ETNM 1.2.4 on RF 3.5b (build 2007102200). I’d be curious to see what happens if two masters don’t contain the glyph. In my minimal window toggling script, I do this to skip over master w/o the current glyph: |
In that case, if you’re in a glyph that is not present in any of the other masters, where do you go? |
If you have various UFOs open, and |
I personally prefer going to the next master no matter what. I think staying on the same glyph is a strong core feature of the extension, but to me it's not necessarily "Edit (this, or nothing, in) Next Master". Even if the next master doesn't have an Maybe it's a behavior preference?
|
One thing to keep in mind – the glyph window is not the only way to toggle masters. There also is a font overview, which probably is better suited to consciously create new glyphs (I honestly don’t know how how I usually create new glyphs – with the previous/next buttons perhaps?) Maybe this is not so much a problem in default mode, more of a problem of the Single Window mode (which I know you’re a user of)? |
Getting the following traceback sometimes,
line 279, in switch
Could the behavior be such that it would go to the next master anyway, but go to a glyph that it has? Or no active glyph? Something like but probably not this?
The text was updated successfully, but these errors were encountered: