UNDO

Has anyone noticed that the undo command is still causing probs in 2.2.0016?My client (I support) lost 3 hours work the other day and wasn't even using lisps that contained any undo statements in them.

Comments

  • There have been several undo fixes since 2.2.0016, and you can see it in the logfile included in the package.One was with the break command: undoing break polyline could cause a crash(it looks like this has never worked correctly). Another was with setvpoint causing the familiar 'drastic undo without redo'.And another was with lisp.currently in 2.2.0025 there are still some undoproblems when calling the predefined undo(.undo, _.undo),fixed in the next build.For the rest, there is undo not seeing xclip, which is not a major bug. Since people actually start using undo again, undobugs become even more important than before and they are still top priority.sander,bricsnet

  • Make him use autosave.

This discussion has been closed.