Eric and Mark, Thanks for your attempts to save my sanity (of course, it could well be too late).
I re-started 3.0, loaded stsMLXEditor, found the first guilty-looking 'save this stack', and commented it out... and then 3.0 crashed before I could even save it! Unbelievable. I couldn't face going through every stack and finding every handler that caused a stack to be saved. What I didn't understand is that I have checked 'preserve stack file version on stacks saved in legacy format' in Rev's preferences. Yet it seemed to be ignoring that in these stacks that have several of their own self-saving events. After searching bugzilla I found that it this is indeed broken: http://quality.runrev.com/qacenter/show_bug.cgi?id=4695. Ken Ray provides a workaround for it: in the MB type: "set the stackFileversion to 2.4;save this stack". After doing that and quitting Rev, the stack is finally in 2.4 and remaining in 2.4. Thanks for your commiserations. I know I must sound like my whining button is stuck on 'loop', but these have been the worst 5 months I've had with Rev in 7 years. Bernard _______________________________________________ use-revolution mailing list [email protected] Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-revolution
