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

Add enharmonic sharp/flat toggle in pattern menu #376

Open
wants to merge 7 commits into
base: master
Choose a base branch
from

Conversation

ebinwalter
Copy link

This addresses #98, purportedly giving parity with yet more trackers.

Questions:

  • Do we want this to be a configuration setting instead of just a per-session toggle?
  • Is this place in the context menu a suitable location for the feature?

Screenshot_20250205_120524

@ebinwalter
Copy link
Author

Thinking about this more, likely it should remain a toggle and not become a persistent setting---plenty of music wherein the key changes halfway through the song, and being able to swap between the two settings without applying changes to config is probably for the best.

@coderofsalvation
Copy link
Contributor

coderofsalvation commented Feb 6, 2025

Makes sense!
Btw. thanks & welcome to the wonderful world of milkytracker.

Could you shorten the 'Toggle sharp/flat display' to something shorter, so that it does not exceed the contextmenu?
Keeping it short is important because milkytracker also runs on tiny devices:

  • Toggle # or b
  • Toggle harmonic
  • Toggle flat notes

Or even better, add the menuitem to:

pattern    >   Transpose
               Advanced edit
               Toggle sharp/flat display

That location is more appropriate for the feature imho, and you don't have to shorten it.
The 'toggle follow' is more related to the playback-engine.

@ebinwalter
Copy link
Author

ebinwalter commented Feb 6, 2025

I think I'll do it under the pattern menu like you said, and 'toggle # or b' sounds like the way to go, since we don't have checkmarks for feedback to show whether the toggle is enabled or not (unless this is broken for already-implemented things on my system?).

@ebinwalter
Copy link
Author

image
Well, there we go. I've also refactored the event to better fit with your advice; it's now BUTTON_PATTERN_ instead of a BUTTON_ABOUT_ event.

Thank you as well for the warm welcome!

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

Successfully merging this pull request may close these issues.

2 participants