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
I'm not sure that it's a good idea to use the term "position" to have two different meanings: one, a vertical offset from middle staff line; the other, a fraction representing a time unit from the beginning of a measure. Seen here in the mid-measure clef change doc:
Parsers would probably use a bare int for the former and an object/struct/class for the latter.
Suggestions to change one of these: for the former include "lineSpace" or "midDistance". For the latter "offset" if not used elsewhere or "timePosition"
The text was updated successfully, but these errors were encountered:
Thanks — great point! Let's go with staffPosition for clefs and leave position for rhythmic position (per our co-chairs chat just now). I'll make the change...
I'm not sure that it's a good idea to use the term "position" to have two different meanings: one, a vertical offset from middle staff line; the other, a fraction representing a time unit from the beginning of a measure. Seen here in the mid-measure clef change doc:
Parsers would probably use a bare int for the former and an object/struct/class for the latter.
Suggestions to change one of these: for the former include "lineSpace" or "midDistance". For the latter "offset" if not used elsewhere or "timePosition"
The text was updated successfully, but these errors were encountered: