As a compromise, how about an autosave feature? It would remove a lot of the risk that comes with not having the ability to undo and - I'm guessing - would be substantially easier to implement.
Starter for 10: 1. Only runs in the GUI. 2. Disabled during test execution. 3. Does not save to the main file but creates a temp file (using a timestamp?) 4. Keeps the last n versions (configurable?). 5. Interval configurable. 6. Can be disabled. 7. By default, uses an 'autosaves' dir in located in JM's tree but perhaps can be pointed elsewhere? Not sure whether the autosaved version should become the master or not, maybe you could update the main file when the test is reloaded. In any case, having this safety net means the worst case scenario is you lose x minutes of work, not hours. ----- http://www.http503.com/ -- View this message in context: http://jmeter.512774.n5.nabble.com/CTRL-Z-as-undo-tp4848249p5160213.html Sent from the JMeter - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@jmeter.apache.org For additional commands, e-mail: user-h...@jmeter.apache.org
