I get it now. The way I work around this is to close all stacks and remove
from memory (or just relaunch LC,) turn off messages in the toolbar, and
open the splash stack. That prevents the other stacks from opening. Build
the standalone and you shouldn't have any trouble, except for remembering
to do the dance.
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On May 3, 2024 5:14:49 PM Bob Sneidar via use-livecode
<use-livecode@lists.runrev.com> wrote:
I think I have solved (but not resolved) the mystery. My main stack has a
lot of behaviors, which of course are enumerated in the stackFiles.
When the standalone is created, the builder closes the copy of the main
stack but it apparently leaves all the COPIES of the behavior stacks in
memory. When I open the original Mainstack, duplicate stacks are still
open. There seems to be no way to delete (close) the copies, because there
is no variable it seems that contains the names of all the behavior stacks
left in memory by the standalone builder. They do not appear in the
openStacks or the stacksInUse. They are not the same stacks as the
stackFiles of the original mainstack.
What really needs to happen, and I have said this before, the standalone
builder needs to keep track of all the files it puts in memory, and then
close them each time a bild is made for each platform.
This is a bug and I will report it as such.
Bob S
On May 3, 2024, at 1:58 PM, Bob Sneidar via use-livecode
<use-livecode@lists.runrev.com> wrote:
Okay I think I traced the issue down to the fact that I “start using” a LOT
of stacks, 64 to be exact, and I think that includes all the behaviors as
well as the libraries. When I quit (or Livecode deletes) the mainStack, it
does NOT delete all the stacksInUse.
I think my solution will be to close all the Stack Files of the main stack
upon closing the Main Stack.
Bob S
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
_______________________________________________
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
