This is 100% cosmetic UX feature that helps when presenting a score, but it is not high-priority.
When organizing scores, sometimes users (aka me) want to have a TD-like visualization (specifically useful for node-based devices (scores acting as state-machines).
One way to achieve this is to use scenarios as subpatches (or sub-scores 😉). It requires a bit of config to make scenario nodes run indefinitely, but it works. What I want to achieve is something like the first image below:
Unfortunately, the zoom level resets once one enters and leaves the scenario:
The expected behaviour would be to have a persistent zoom level on scenarios and nodes. That would also allow us to make specific process parameters from a sub-scenario always visible for interaction, e.g., having the image position visible to interact with:
This is 100% cosmetic UX feature that helps when presenting a score, but it is not high-priority.
When organizing scores, sometimes users (aka me) want to have a TD-like visualization (specifically useful for node-based devices (scores acting as state-machines).
One way to achieve this is to use scenarios as subpatches (or sub-scores 😉). It requires a bit of config to make scenario nodes run indefinitely, but it works. What I want to achieve is something like the first image below:
Unfortunately, the zoom level resets once one enters and leaves the scenario:
The expected behaviour would be to have a persistent zoom level on scenarios and nodes. That would also allow us to make specific process parameters from a sub-scenario always visible for interaction, e.g., having the image position visible to interact with: