On Tuesday 29 April 2008 09:00, rgheck wrote: > Steve Litt wrote: > > Hi all, > > > > I'm not going to call this a bug. > > Sounds like it is a bug to me.
Whatever it is, the last time I brought this up someone came up with an idea: Throw up a clear error message that your doc has changed, and not for the better, and strongly urge saving under a different name, and throw up a save window defaulting to an intelligent different name. If that had happened, I'd have preserved my existing file as the last known good version, and continued to troubleshoot, but without the uncertainty that I missed one or two custom styles in a 150 page book. I have an improvement on even that. Just before the code that changed the document class, do this: 1) Save the current, in memory SOURCE to myfile_b4_revert.lyx 2) Throw up a big, hairy error message telling them something's very wrong 3) Throw up a save dialog defaulting to myfile_after_revert_probably_wrong.lyx 4) Throw up an info screen explaining the situation and the options. I haven't looked at your code, but to me this looks like a small, localized change that doesn't in any way change your basic architecture. As far as I can see, the only information needed to be captured is the name of the original document. Normally I'd say "we're already giving them a warning: if they don't heed it, tough!" But this particular situation can lead to what for many could best be described as total destruction of their document, so strong safety structures should be placed. It's very similar to putting a very strong rail on a curve in a mountain highway where if you go off the road you fall 200 meters. SteveT Steve Litt Author: Universal Troubleshooting Process books and courseware http://www.troubleshooters.com/
