Pitch preview functionality and user overrides for accidentals (sharp, flat, and their doubles)

[pikurasa]

Pitch preview is helpful in many contexts, such as if you want to compose something in a particular non-c major key.

However, if you are in a key and your intentionally override an accidental, when you click the pitch again to open its pie menu the accidental you chose is overridden by the in-key accidental. This can be unexpected and bothersome.

One idea we thought of today is a (hidden) flag to indicate whether a pitch accidental has been overridden. Pitches with this flag would not be re-adjusted by pitch preview.

If we do this, it opens up other questions, such as how persistent will this state be? Does it stay with the block? Is it saved?

Since it is more bookkeeping, we also need to consider whether or not a feature would be sincerely worth the time.

[walterbender]

one example of persistence is when you copy a pitch block (or note block with a pitch block).