You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following toolbar items' states should be saved in project files and restored on load:
Selected tool (pencil, knife, box select)
Auto-scroll on/off
Zoom amount
Snap size
Relative snapping on/off
Justification
Personally, I'd very much like to disable auto scroll by default, and don't currently care that tool selection, zoom, and snap settings aren't saved in project files. However, previous discussion on playhead stop behavior (among other things) shows us that:
Thanks to workflow differences, every configuration is likely to have some proponents
If this is true, any change to a default will worsen some user's experience
These users have no reason to make themselves known until after the change is proposed or implemented
Thankfully, default templates mean that saving state in project files makes it user configurable without cluttering our settings menu. So, rather than playing whack-a-mole by adding state save/load whenever disagreement appears surrounding some default setting, I propose that we save the full state of the song editor toolbar in projects. This should also allow a more objective discussion of which defaults should potentially be changed, as no one will need to feel that their personal workflow is being threatened.
The text was updated successfully, but these errors were encountered:
Spekular
changed the title
Song editor: save/load full toolbar configuration in project files
Song editor: save/load full toolbar state in project files
Oct 9, 2023
Enhancement Summary
The following toolbar items' states should be saved in project files and restored on load:
Justification
Personally, I'd very much like to disable auto scroll by default, and don't currently care that tool selection, zoom, and snap settings aren't saved in project files. However, previous discussion on playhead stop behavior (among other things) shows us that:
Thankfully, default templates mean that saving state in project files makes it user configurable without cluttering our settings menu. So, rather than playing whack-a-mole by adding state save/load whenever disagreement appears surrounding some default setting, I propose that we save the full state of the song editor toolbar in projects. This should also allow a more objective discussion of which defaults should potentially be changed, as no one will need to feel that their personal workflow is being threatened.
The text was updated successfully, but these errors were encountered: