Page 1 of 1

Compilling a standalone - stack in memory

Posted: Mon May 06, 2013 5:07 pm
by rjuan
Saving a standalone application was working and now it doesn't. I don't understand why I have this alert :
A stack "revCopiedIcons" is already in memory. The Revolution UI does not distinguish staks which have identical names, so editing these stack files while both are in memory could result in data loss.
Since I got this message after opening my main stack, the standalone app can't be done properly and I have a long text error beginning with
There was an error while saving the standalone application ... lots of numbers & commas... revCopyIcons...
I do not remember I did add stacks or files.

Re: Compilling a standalone - stack in memory

Posted: Mon May 06, 2013 5:52 pm
by jacque
Go to the User Samples (in the LiveCode toolbar) and search for "error lookup". There's a stack there that will tell you what all those error numbers mean.

The first error probably means that you included icons in your first build and they somehow got attached to your stack. Look in the Application Browser for a substack named revCopiedIcons and delete it.

Re: Compilling a standalone - stack in memory

Posted: Tue May 07, 2013 5:40 pm
by rjuan
I search for "error lookup" and find powerdebug, but when I downloaded it, couldn't find where it is to launch the stak.
I do not know where it was downloaded on my mac.

Anyway I got rid of it taking a fonctionnal backup and updating it.

Re: Compilling a standalone - stack in memory

Posted: Tue May 07, 2013 7:25 pm
by jacque
In User Samples, make sure the "All" or "Stacks" category is selected. Then search for "error lookup" or "LiveCode Error Lookup". When I do that, the stack is the last one in the list. PowerDebug is a powerful debugger alternative, but it isn't the lookup stack. :)