Version 2.0.34

[Hares]

While it happens to me sometimes, that undo is just not feasible due to the large number of ctrl-z to undo a single drag, I would prefer some option for ctrl-z undoing whole drag. Like said before, fibonacci-pattern on undo or option in menu, or (we don't have enough keys yet!) a modifier key (shift?).

Ctrl+Shift+Z would be AMAZING for that!
The feature/action could be called "Greedy undo"

[Lorenzo]

Ctrl+Shift+Z would be AMAZING for that!
The feature/action could be called "Greedy undo"

+1

[meganothing]

This may be a rather ignorant view as I haven't tested the change yet, but "undo" in UI design is primarily a method to go back on mistakes, not for efficient building or speed runs. And the intuitive thing for the user is that any **action he does** is undone one by one, not suddenly split into hundreds of small actions the game has to do to to fullfill that single command. Otherwise the user would have to know details about the implementation of his actions.

So the change is very reasonable in my view. (There still could be an option or both available with different keys as some have proposed, but reverting it would be wrong IMHO.)

[thecatlover1996]

While it happens to me sometimes, that undo is just not feasible due to the large number of ctrl-z to undo a single drag, I would prefer some option for ctrl-z undoing whole drag. Like said before, fibonacci-pattern on undo or option in menu, or (we don't have enough keys yet!) a modifier key (shift?).

Ctrl+Shift+Z would be AMAZING for that!
The feature/action could be called "Greedy undo"

Except that my muscle memory uses Ctrl+Shift+Z for "redo"

[Hares]

Ctrl+Shift+Z would be AMAZING for that!
The feature/action could be called "Greedy undo"

Except that my muscle memory uses Ctrl+Shift+Z for "redo"

There's no such thing as hardbind, you can always use your favorite hotkeys configuration

[mgabor]

+1 for reverting the `signal-ghost` removal.

That is the only thing that got removed, making it the only breaking change in the update.

I would very much prefer if this was re-added before the change goes out of experimental, this would "break" almost all miditorio.com builds.

("Break" might be an overstatement. A few notes would be removed from the song. But still.)

Migrating it to one of the new signals would work too, but then I'd need to change it in the blueprint generation.