Errors When Saving as Stand-Alone Since Rev 4 Upgrade

[stephenmcnutt]

I've got an application I've been building and tweaking for years, but since I upgraded to the latest version of Revolution (the upgrade that involved the Revolution icon change), I get warning dialogs when saving as a stand-alone. I get one that says:

A stack "answer dialog" in file /Users/Steve/Desktop/Classroom Quizshow MacOSX/Classroom Quizshow.app/Contents/MacOS/Classroom Quizshow.rev is already in memory. The Revolution UI does not distinguish stacks which have identical names, so editing these stack files while both are in memory could result in data loss.

I get that message maybe 10 times during the stand-alone creation process. I also get the following dialog once during the stand-alone build process:

A stack with the same name as the one you are trying to load is already open. Before loading /Users/Steve/Desktop/Classroom Quizshow/MacOSX/Classroom Quizshow.app/Contents/MacOS/Classroom Quizshow.rev, what do you want to do with stack: /Users/Steve/Documents/CQ latest build/Classroom Quizshow.rev, Classroom Quizshow? with options Save, Purge, and Cancel. I choose Purge but don't know why.

I finally get a message saying the stand-alone was saved properly, but it doesn't work properly. Specifically what doesn't work properly is that changes like new sets of questions or new teams are not saved when the application is closed and reopened. These changes are supposed to be saved to substacks contained within the application. It has worked for years, but now it doesn't.

I confess that I've never understood what the "purge from memory" setting does. That second dialog message seems to have something to do with that.

The first dialog message really confuses me, though, because there is no stack named "answer dialog" in my application--not one that I explicitly created anyway--although of course I do use the Answer function. Help?!?!? And thank you in advance for even reading this far.

[massung]

I reported this one very quickly once 4.0 came out. It's still not fixed, but several of us were able to track down the cause (albeit, I don't remember what it was... I'm sure if you search the forum's you'll find it).

However, I do know that it only happens when you are building for several platforms at the same time. If you just build each target platform one at a time, this problem won't ever happen. A simple work-around. I believe I saw in the patch notes for 4.5 that this issue has been resolved completely. Hopefully RunRev wouldn't ask existing users to pay for an upgrade to fix a hefty bug (as opposed to just providing a patch for 4.0 users who didn't want to upgrade).

Jeff M.

[shadowslash]

A stack "answer dialog" in file /Users/Steve/Desktop/Classroom Quizshow MacOSX/Classroom Quizshow.app/Contents/MacOS/Classroom Quizshow.rev is already in memory. The Revolution UI does not distinguish stacks which have identical names, so editing these stack files while both are in memory could result in data loss.

This happened to me on one of my time-critical projects before. It even got to a point where I can't save the stacks for God knows why, but luckily my 14-year-old sister popped in and said she saw a clone command from the open documentation window and thought it could help. I tried it and not only did it work for the Answer Dialog error, it also enabled me to save my source and prevented me from actually wasting 1 year of testing and building. Another good thing is that I didn't close the revIDE when that happened. Doing that might render the source useless.

Just sharing my experience though...

[stephenmcnutt]

Wow. Thanks to both of you (Jeff and Shadowslash) for helping me out with this bug. The Revolution community sure is friendly and helpful. I don't know what you mean about the clone command, though, Shadowslash. Mind explaining that a bit more? Nice to have a smart 14-year-old sister hanging around, huh?

[Mark]

stephenmcnutt,

I have posted 18 reasons why building a standalone may fail and what you can do about it at http://blog.schonewille.tk/ . Please, let me know whether this helps.

Best,

Mark