A stack "revCursors" is already in memory.
bobsneidar at iotecdigital.com
Fri Jul 7 11:43:20 EDT 2023
Correction: revSaveAsStandalone. Not even sure that is it though. For some reason I removed the bits of code where I was using this. Putting revSaveAsStandalone in the dialog box produces nothing, so it may be a global that gets created when a standalone is being built, and gets deleted when done.
> On Jul 6, 2023, at 3:39 PM, Bob Sneidar via use-livecode <use-livecode at lists.runrev.com> wrote:
> What happens is that when you build an app, every stack it uses will be opened in the IDE, ostensibly to determine what inclusions are necessary. I have seen where the version of the stack that is open AFTER building the standalone is the one in the STANDALONE! So if you continue to use the IDE or try to build another app, you will get that conflict. That *may* be what you are experiencing, although that may have been addressed in 9.6.9 or some subsequent release.
> To avoid this altogether, I quit the IDE every time I build an app per platform so I do not encounter that. The first time it happened, I saved my stack and it replaced all the references to the stack files with the version from the standalone! I had a hell of a time cleaning it up!
> There is code you can put at the beginning of certain handlers like preOpenCard where you can check the value of the global variable reSaveAsStandalone (or something like that) and then exit accordingly, I forget the list of handlers you need to use this on. I think preOpenCard, preOpenstack, openCard and openStack. But if you do this, then you cannot use the Auto Inclusions feature. Really a bummer.
> I suppose you could trap for revSaveAsStandalone in your openCard handler of your main stack, then run a routine that registers all the stacksInUse, then when the standalone finishes, run a routine that closes those stacks by name, then reopens the correct versions, but that is a LOT to have to do for a feature so fundamental as building a standalone.
> Another thing building standalone does is it adds every stack the IDE opens to the recents list! BOOOO!!! BIG BAD BELLOWING BLUSTERY BOOOOOOO!!!!!!! The handler that does that should ITSELF be checking the status of revSaveAsStandalone!
> Bob S
>> On Jul 6, 2023, at 2:28 PM, Paul Dupuis via use-livecode <use-livecode at lists.runrev.com> wrote:
>> On 7/6/2023 5:12 PM, J. Landman Gay via use-livecode wrote:
>>> On 7/6/23 9:26 AM, Paul Dupuis via use-livecode wrote:
>>>> I have a new Livecode 9.6.9 install on a new Windows 11 laptop. It was working normally for a while, and, now, whenever I launch it, I get a warning message:
>>>> A stack "revCursors" is already in memory. The Livecode UI does not ... etc..
>>>> Can someone advise what I need to do to address this? I seem to recall this problem has been seen before.
>>> I think it happens when you include cursors in a standalone build. Sometimes LC adds it to your stack as well as to the executable. When LC launches it see both the one in the stack and the one in the IDE.
>>> Check the substacks of your mainstack. If revCursors is in there, delete it.
>> Thank you. that was the problem. I don't recall adding revCursors to my app's mainstack, but I did get a code execution error during a standaloneSaved handler before this started happening, so perhaps it left the build in a strange state. Fixed now. Thanks again.
>> use-livecode mailing list
>> use-livecode at lists.runrev.com
>> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the use-livecode