The undo functions are very limited at the moment. it would be nice if there were more actions that can be undone... i thought about moving / removing channels. of course, saving all patterns before the (re)moving action would not work, but there could f.e. be a variable the saves which channels are moved from where to where...
Absolutely agreed. A history list would be nice.
jupp... waiting for that quite some years
Theoretically we could backup CSoundFile struct (read: whole module file) after each keypress. That will probably require gigabytes of RAM :) and will slow MPT down ;) . So it should be optional.
We may always raise hardware requirments to handle this ;) .
You don't actually have to backup the struct every time... You only need to save what has changed - an incremental undo feature. So removing a channel would only save that channel's info... This wouldn't use up too much ram, and you could always let people choose an arbitrary level of undos (or amount of space to use storing undo info).