Well, Maybe As An Option
#68 posted by XaeroX on 2015/06/06 22:18:27
Selections and object properties (which are currently also non-undoable) will blow the undo buffer up.
#69 posted by
JneeraZ on 2015/06/06 23:34:19
Have a limit. Most apps will give you an option where you can set the number of undos you want. So if someone has a monster machine, they can jack the number up higher.
Also, something I've seen done is clearing the undo buffer whenever the map is saved. ToeTag does that...
So Does TB
Also, there really is no need to limit the undo buffer. You can collate subsequent actions into one (for example, you can collate 5 subsequent transforms if they happen within a certain amount of time) and the actual information you have to store is quite small for most operations in a level editor.
Oh God No!
#71 posted by XaeroX on 2015/07/06 00:13:30
>>clearing the undo buffer whenever the map is saved
This is the most evil feature I've ever encounetered.
Once I've lost my work in Excel after occasional Del followed by Ctrl+S instead of Ctrl+Z!
#72 posted by
JneeraZ on 2015/07/06 00:25:07
Whether it's more or less evil than only including certain actions in the undo/redo buffer is a debate for another time then. ;)
#73 posted by XaeroX on 2015/07/07 15:01:18
Well, excluding selections from undo buffer can't be fatal as compared to deleting or modifying objects, you can always select again and you can't break the work with unwanted selection.
As for entity properties, well yes, this is evil. But afaik VHE doesn't undo them too, and I was too lazy to implement it since it doesn't fit well to my undo system. :(
Am I Missing Something Here?
#75 posted by
Orl on 2015/07/07 19:03:10
I have always been able to undo everything I've done with Jackhammer after saving a map with no problem.
#76 posted by
JneeraZ on 2015/07/07 19:25:49
Yes, you're missing something. The previous 10 posts or so should clear it up.