Standalone - stack already in memory and revMacCursors

[jameshale]

Hi,

I am in the process of building an app (Mac, iOS and Android) and so have been building quite a few standalones.

Two things have kept coming up.
1. Alerts about mystack" is already in memory" and
2. Alert "stack "revMacCursors" is already in memory.

I have discovered that to get rid of 1 and 2 (after something else) I need to close ALL open windows within the IDE with the exception of the stack I am building of course before building. Once all are closed the build goes though without the alerts.

The something else I mentioned above was to check your stack AFTER getting (2), say in the project browser, and delete the "ravMacCursors" substack that will have been added. Why it gets added I don't know, but (2) will keep returning until it is deleted.

Note the above doesn't happen every time I build the standalones but enough to p**s me off.

So now I try to remember to close all open windows before building.

oh yes, I am using the lastest builds of LC and MacOS 11 (can't run Monterey )

[dunbarx]

James.

I see the "Cursors" dialog every time I build a new version of my main project. I ignore it. There are threads about this, but it seems to do no harm. I also see the memory thing, even when I believe that I am working on a newly named variant of an older version. Sometimes I am asked to purge the old version. I always do, and never have had an issue.

So except for the slight annoyance, I just hit a few buttons and keep going...

Craig

[jacque]

I've heard several complaints about both behaviors but I have never seen either of them. I wonder if it has to do with some settings.

In the message box, set the destroystack of the stack to true. I have my LC prefs set to create all new stacks with that setting. This way when you close the stack it's removed from memory. When LC builds a standalone it opens and closes the stack so this setting may be affecting it.

In standalone settings, make sure you have chosen to select inclusions manually. Then check the Inclusions pane to ensure that revMacCursors are not selected. If you have been allowing LC to scan for inclusions, it may be adding the cursors by default.

[dunbarx]

Jacque,

Hi.

I have those same settings (destroyStack and manual inclusions), and always see these things. The "stack already in memory" comes up, as I said, even when opening an older version that has a different name to check on what I did wrong between then and now.

Craig

[jameshale]

yes I also have the settings set as described.
I just click "Save" when the same stack dlog appears when it happens, but the revMacCursors substack is really bizarre.
I have no idea what is prompting LC to add it to my stack.
I wish I could point to a recipe but it just seems random as it does occasionally happen even if I remember to close all windows.
oh well.

[jameshale]

Ah Apologies.
Just checked stand alone setting and find I do have the "cursors" included.
given I don't require any (apart from the normal OS pointer) I excluded and rebuilt.
All seems fine.

[FourthWorld]

I'm curious: do you see "revMacCursors" among the output from running this in the Message Box:

Code: Select all

put the substacks of stack <mainstackname>

... where "<mainstackname>" is the short name of your mainstack.

[jameshale]

Only if the revMacCursors alert appears.
Than I need to de7 the substack from my project as it has been added.
If the alert does not appear the substack is not added.
So somewhere during the build process, LC adds it.

[SteveFI]

I was going to say "check your substacks" because I once suffered a crash during the build process (restrictions had been added to my computer, so it couldn't write something to where it needed to) and the cursors stack had been added to my mainStack and saved.

I just had to go and delete the substack and all was fine afterwards (and tell off IT for complicating my life).

Steve