On Friday afternoon I spent about 30 mins doing drawing edits.
I had to undo a single line placement and it instead undid everything since I opened the file.
I tried clicking redo and it all came back....
I thought this really odd, so I saved the file and closed it.
I re-opened it to test and 'undo' appeared to work as normal, ie the undo button would only undo one step at a time.
I continued working for another 30mins, went to undo something, and again, it undid everything for the last 30mins, only this time it crashed in the process. When I re-opened the file I'd lost 30mins of work.
I understand there is now an option to "set a mark" in the undo tool - however I have not used this.
I have also been using the undo tool from the "standard" toolbox menu, not the ribbon menu.
This is not normal behaviour obviously.
The undo tool in both places issues the 'undo' command, as does 'Ctrl + Z'.
Has this occurred with just one file or have you seen it with other files?
I suggest compressing the file before starting work on it, select all options.
OBD saves every time it spots a (very) brief pause in user activity.
As you work are you seeing the save icon (floppy disk) persisting? It should disappear as soon as you pause:
Regards
Marc
same undo problem has happened to me too recently. ctrl+Z undos all & same does the undo icon in Quick Access Toolbar. it doesn't help even if you disable undo_all & undo_to_mark in Quick Access Toolbar.
after compressing the file problem disappears.
had the undo problem too. compress fixed me.
Which version are you using?
We have had reports of Undo stepping several steps back but unable to redo to recover Marc. In this case ORD 10.9.1
Please can you post this in the OpenRoads forum as there could be product or version specific aspects: communities.bentley.com/.../geopak-inroads-mx-openroads-forum
We have this problem intermittently also Marc, It used to occur regularly in earlier versions of MS Connect but generally seemed to stop a couple of years ago, though recently I have had reports from users of the same. We are generally unable to replicate the issue so I have been unable to file any SR's on it. Only happens for some people, some of the time, not always the same people, but definitely not consistently across the office which leads me to believe it is some kind of prefs issue