Page 3 of 3
Re: Stack allready in memory
Posted: Mon Jan 08, 2024 7:34 pm
by richmond62
Are ask/answer windows a type of substack?
Re: Stack allready in memory
Posted: Mon Jan 08, 2024 8:15 pm
by Klaus
Only in a standalone!
In that case LC makes them substacks of the runtime-stack.
Re: Stack allready in memory
Posted: Mon Jan 08, 2024 8:30 pm
by SparkOut
I will posit a scenario where the OP has the two individually named stacks in the Community Edition v 9.x.x and realised that he cannot password protect them when building a standalone.
Then the OP opened the older Rev Studio 4.0 IDE to make the standalone build with password protection, but either he or the Community IDE somehow failed to close and remove from memory. (I have seen occasions where the visible windows disappear but the running task list still shows LiveCode running.)
I don't know how plausible this scenario is (I think it might be expected that each version of the IDE opens as its own instance so could have the stacks concurrently open. On the other hand, if one IDE marks the stacks as open, then the other might call foul. I haven't been able to test.)
Re: Stack allready in memory
Posted: Mon Jan 08, 2024 8:35 pm
by richmond62
Only in a standalone!
In that case LC makes them substacks of the runtime-stack.
Does building a standalone ONLY make ask/answer windows substacks in the standalones that are hived off the source stack, or does it make them substacks of the source stack BEFORE it hives off the standalones?
Because if the second situation is what happens that could make things a bit difficult if the programmer then subsequently opens the source stack for further editing.
Re: Stack allready in memory
Posted: Mon Jan 08, 2024 8:49 pm
by Klaus
richmond62 wrote: ↑Mon Jan 08, 2024 8:35 pm
Only in a standalone!
In that case LC makes them substacks of the runtime-stack.
Does building a standalone ONLY make ask/answer windows substacks in the standalones that are hived off the source stack, or does it make them substacks of the source stack BEFORE it hives off the standalones?
Because if the second situation is what happens that could make things a bit difficult if the programmer then subsequently opens the source stack for further editing.
LC creates a COPY of the runtime stack in the TEMP folder and turns that one into a standalone,
including making the ASK/Answer dialogs substacks of that namely stack.
So the initial stack remains "untouched".
Re: Stack allready in memory
Posted: Tue Jan 09, 2024 9:13 am
by richmond62
Thanks Klaus, although brings us no nearer to an answer.