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

getting the context name #45

Open
jefferyshivers opened this issue Aug 30, 2016 · 1 comment
Open

getting the context name #45

jefferyshivers opened this issue Aug 30, 2016 · 1 comment

Comments

@jefferyshivers
Copy link
Member

When not explicitly set in the annotation properties, context (or context-id) defaults to the name of the directory containing the project file.

I haven't looked into the mechanics of this functionality yet, but think it would be good to update it to:

  • Automatically check for staff/instrument names that could've been set by the user
  • Use that unless the context property is set explicitly as an individual annotation property
  • If none of those are set, only then resort to the directory name (I guess)

Not speculating any problems with how it currently is programmed, just thinking this change would be better.

@uliska
Copy link
Contributor

uliska commented Aug 30, 2016

I'll look into that after my holidays. But IIRC it doesn't directly default to the directory name (which I agree will make sense only in specific set-ups) but first tries to get other meaningful data auch as Voice/Staff names.

However, I'm aware that this could be made somewhat more failsafe.

Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet.

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

No branches or pull requests

2 participants