Skip to content
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

Position: two meanings #323

Closed
mscuthbert opened this issue Feb 22, 2024 · 1 comment
Closed

Position: two meanings #323

mscuthbert opened this issue Feb 22, 2024 · 1 comment

Comments

@mscuthbert
Copy link

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:

image

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"

@adrianholovaty
Copy link
Contributor

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...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants