make instrument change undoable

[grindhold]

I often experiment around with how a track would sound if played with other instruments. However drag-n-dropping a new instrument or preset into a track is not undoable yet. Sometimes it's especially annoying when you place an instrument by accident into the track beneath or above the track you initially intended to drop the instrument on. In this case i often dont remember what instrument was in the other track to fix my mistake.
Being able to undo instrument changes would be very convenient.

[Sti2nd]

Totally agrees on that, you can code that?

Note: I don't think we should file a new bug for everything which isn't undo-able. The only thing which is undoable is changed on notes in the Piano Roll

[grindhold]

i could try coding that ;)

i don't quite get your sentence. did you mean "the only other thing which is undoable..."?
because i stated at least one other possibility in my original post, that you also confirmed.

I'll wait with coding new stuff until my current stuff gets reviewed and eventually merged. I have other projects too and i don't want to get too much issues parallel.

[tresf]

@grindhold, we are so short on developers, you come as a breath of fresh air.

What @Sti2nd is asking is if you can make undo work everywhere in the software 😈 . Naturally this is a loaded question!

These types of questions are something you'll learn to expect from the more "enthusiastic" members of our community. :)

Thanks for showing interest in helping fix this software! Vesa and Toby generally review and approve the C++ pull requests and they generally do so in a timely manner. :)

[Sti2nd]

Yes, I meant that "undoable". I only requested him to try to make undo/redo possible for instruments (that would include knobs), but of course I want you to make undo/redo everywhere 🍒

[grindhold]

okay, of course i cannot promise to find and fix any undoable command in the program.
I am also not in favor of @Sti2nd's request not to open an issue for every occurence of the problem.
issues should be small and well-defined. a "fix every nonexistent undo"-issue would be an unclosable endless-issue.

[curlymorphic]

#1284 It was decided to handle this in 2.0

[tresf]

Bumped (to 1.3 for now). Thanks! 👍

[SecondFlight]

As part of a pruning effort, this enhancement request is archived into a dedicated "Better Workflow" checklist here #4877.