There are a number of things that will prevent destroyStack from
working. It will fail if the stack is in use, if there is an open
socket, if there is an open driver, and maybe some other things I can't
remember. Basically, if any part of the stack is still in operation it
can't be purged.
On
yup
Bob S
> On Sep 5, 2018, at 11:34 , Knapp Martin via use-livecode
> wrote:
>
> Did you check revLoadedStacks()?
>
> Marty
>
>> On Sep 5, 2018, at 11:25 AM, Bob Sneidar via use-livecode
>> wrote:
>>
>> Hmmm... I have all three set on my mainstack and when I close it, the stack
>> and
Did you check revLoadedStacks()?
Marty
> On Sep 5, 2018, at 11:25 AM, Bob Sneidar via use-livecode
> wrote:
>
> Hmmm... I have all three set on my mainstack and when I close it, the stack
> and it's substacks are not in memory. However, stacks I started using are.
>
> Bob S
>
>
>
>> On S
Hmmm... I have all three set on my mainstack and when I close it, the stack and
it's substacks are not in memory. However, stacks I started using are.
Bob S
> On Sep 5, 2018, at 10:49 , Knapp Martin via use-livecode
> wrote:
>
> To answer my own question, although the Property Inspector wi
To answer my own question, although the Property Inspector will allow you to
set both the destroyStack and cantDelete properties of a stack to true,
cantDelete (when true) blocks destroyStack. I’d set cantDelete to true so that
I wouldn’t accidentally delete a stack or sub stack. But generally,
I have all my stacks configured with destroyStack and destroyWindow (gotta love
those names!) set to true. And yet after I close them, if I check the
revLoadedStacks() it shows that they and their subStacks are still loaded in
memory. What do I need to do to get them out of memory?? Using LC 9.0
How would the engine know whether that behavior is used elsewhere, or will
be needed in the stack that opens next? The easiest way to get the behavior
you want, without any scripting, is to put the script in a button in the
stack. Then when the stack is deleted, the behavior is gone.
If you're
I was thinking the same thing. I'm pretty sure that when an app for Windows
uses DotNET Framework, it takes some time to initially load the framework, then
the app can launch. Once the app is quit, I do not think it unloads DotNET
Framework, because the next time I launch the app, the process is
Sannyasin Brahmanathaswami wrote:
> When we delete a main stack, the main stack and all its substacks are
> removed from memory.
>
> But if we delete a stack that has behaviors set from external
> *_behavior.livecodescript stacks for controls in the "main"
> (parent?) stack, those behaviors are
When we delete a main stack, the main stack and all its substacks are removed
from memory.
But if we delete a stack that has behaviors set from external
*_behavior.livecodescript stacks for controls in the "main" (parent?) stack,
those behaviors are still in memory.
Does it make sense to file
ok, got it working. Thanks for everyone's help. Here is what I have
done,
The launcher has a datagrid AppPicker contains the links to the files
available to launch.
on mousedoubleup
set the itemdel to tab
put the dgHilitedLines of grp "AppPicker" into tLine
put the dgDataOfLine[t
stephen barncard wrote:
> On Tue, Feb 16, 2016 at 10:54 AM, Mark Waddingham wrote:
>
>> delete stack
>
> which is the scariest command in the language for newcomers, because
> we often call the stack FILE 'the stack'.
One possible remedy - a new "purge" command so the behavior is less
frighten
On Tue, Feb 16, 2016 at 10:54 AM, Mark Waddingham wrote:
> delete stack
which is the scariest command in the language for newcomers, because we
often call the stack FILE 'the stack'.
The first few times un-mounting a disk by dropping it into the trash can
was pretty distressing too.
Stephen
On 2016-02-16 19:11, Michael Doub wrote:
I am building a launcher app the loads stacks from DropBox.
I am using
go URL tURL where the tURL is the stack to load using the correct
DropBox format.
This works great for the first load. However, if I update the stack
in DropBox and try to reload tUR
Thanks Scott, but no luck. This might work if I was using the same
url. In my case I have two urls that point to separate files. file1 is
rev 1 of the stack, file1 is rev 2 of the stack. The stack inside each
file has the same name, but different code.
load file1 you see version 1 of t
I use the "revert" command. It basically just means "reload from disk" .
--
Jacqueline Landman Gay | jac...@hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On February 16, 2016 12:14:15 PM Michael Doub wrote:
I am building a launcher app the
Try this, posted by Mike Bonner a while back:
"Like the timestamp, you can just tack on a # and the milliseconds to each
request. http://whatever.url.com/mystack.livecode#134513461";
Regards,
Scott Rossi
Creative Director
Tactile Media, UX/UI Design
On 2/16/16, 10:11 AM, "use-livecode on be
I am building a launcher app the loads stacks from DropBox.
I am using
go URL tURL where the tURL is the stack to load using the correct
DropBox format.
This works great for the first load. However, if I update the stack in
DropBox and try to reload tURL, it does not purge the existing stack
18 matches
Mail list logo
