Undo history

Question

I'm looking for a way to list every action performed so I can scroll said list and undo to a desired point and redo if so desired. Design history does not satisfy this need because to achieve what I want I would have to literally use the commit changes command for every single mouse click I make. Surely there's a simpler way to achieve this task? 
 Here are some examples from other simpler programs: 
 paint.NET - A bitmap image editor.

REAPER - A Digital Audio Workstation (DAW) 
 
 Is there not a way to list similar metadata within microstation?

Keith Ericksen · Answer

I know of two things you may find useful: 
 1. You can set a mark and undo to the mark (keyin: MARK). This would be useful when performing steps where you may not be sure of the outcome and you want a quick fall-back via UNDO MARK 2. You can also undo multiple steps at once using the keyin undo n, where n = an integer value of the number of steps you wish to undo. Note there is no redo n. 
 Beyond that, I know no way of capturing each command's output to be used as a guide to know how far to step back. Possibly, this could be done with a macro, but I would be very reluctant to use that approach because the macro would be running continuously, capturing command input, writing it out and then issuing the same to Microstation for processing -- very complex and a lot of overhead.

Keith Ericksen · Answer

I would agree that it probably wouldn't be too difficult for Bentley to add this feature. Just not sure how many users would value it. You could always enter it as an enhancement request.

Lorys · Answer

no real simple way possible in any cad pack to track ALL changes I can think of.. however there is a very expensive way from bentley its called Projectwise... 
 and you check out a drawing make a change and check back in and use the new version option.. you can at anytime choose a previous version... and when up versioning you can add a comment the audit trail lets you know when it happened.. but its still limited and you cant list every action it would drive you mad... 
 I use it for major design changes... 
 Before pwise I used to do copy the default model from the model icon options and name the copy by date and the default model is always the current model the other models are the older ones at the time of copying and some short comment and you can self ref and use high light ref to see the changes.. it does make your file get bigger but it works pretty well no extra costs ..you can add comment or some non printable level text in the model itself ... 
 I would also recommend the compress option and data clean up utility delete duplicate elements be used often 
 to do a self ref key in is RF=. ( RF= dot) then choose which model and world coincedent.. 
 you can set the ref to hilighted or use and override colour for all the levels for just that model and then you can see before and after at the same time but again only use this method for major changes... it would take too much time for every minor change.. the multimodel approach is probably your best fast cheap option and not much of a learning curve...

Undo history

Top Replies