Well, something really stupid seems to be happening in this regard. When one needs to open a DP file that has been auto saved, (meaning unsaved changes were spotted by DP, and it asks you if you want the more recent version), (which should be called butt save), DP will indeed allow a user to save the "more recent” version, asking you to give it another name. This can allow a user to recover work and is a good thing. But in the true MOTU spirit of “one step forward, two steps back”, when your butt gets saved this way, and you save a “new” iteration, thereby recovering “lost work”, , DP opens your “recovered file”, without any undo history. Very dumb! I need my undo history, and I never erase it. I use it for time log documentation for record companies, and, I use it in case I need to go back in time. So the result of this is I have learned that any time DPs auto “save” saves my butt, it loses its mind, omitting the entire undo history in the recovered file, Dumb!
Why is DP programmed to act this way? Why does recovering an auto save file necessitate losing one’s undo history? Makes no sense in practical terms, and gives any user a loss of data should they want to “recover” data.
As an experienced user, I figure the work around for this ridiculous programming error in DP, would be to get the new data from the “auto save” version, and import it BACK into the previous version, thereby recovering my undo history. But that could get very complicated depending on what work was created in the auto saved version. But really , I want to know why why why, it needs to be this way, and what sense this makes? Oh DP, sometimes you break my heart.
