Author Topic: Better undo functions?  (Read 3042 times)

Offline Saga Musix

  • OpenMPT Developers
  • *****
  • Posts: 6,641
  • aka Jojo
    • Download music, samples, VST plugins: Saga Musix Website
  • Operating System: Windows 10 x64
Better undo functions?
« on: May 19, 2007, 18:36:05 »
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...
ยป No support, bug reports, feature requests via private messages - they will not be answered. Use the forums and the issue tracker so that everyone can benefit from your post.

Offline KrazyKatz

  • Crazy artist
  • ****
  • Posts: 645
    • http://www.sonicbrilliance.com
Better undo functions?
« Reply #1 on: May 20, 2007, 22:35:45 »
Absolutely agreed. A history list would be nice.
Sonic Brilliance Studios
http://www.sonicbrilliance.com

Offline BooT-SectoR-ViruZ

  • Workaholic artist
  • ***
  • Posts: 468
    • http://breakcorezecke.de
Better undo functions?
« Reply #2 on: May 21, 2007, 11:07:44 »
jupp... waiting for that quite some years
10 years on ModPlug... f#cking hell...

Soundcloud for B-S-V | Soundcloud for DX4-100 | Bandcamp for B-S-V

Offline pelya

  • Workaholic artist
  • ***
  • Posts: 108
Better undo functions?
« Reply #3 on: May 21, 2007, 11:33:12 »
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 ;) .

Offline bvanoudtshoorn

  • Extreme artist
  • *****
  • Posts: 1,053
  • Gender: Male
    • Barryvan
Better undo functions?
« Reply #4 on: May 25, 2007, 03:31:29 »
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).