Thanks Craig,
Your thoughts on this are much appreciated. Darn right about the dangers!
Gregory
On Mon, Sep 12, 2011, at 1:00 PM, use-livecode-requ...@lists.runrev.com wrote:
> Gregory.
>
>
> Glad to see you have worked it out. It is a subtle danger, that other
> messages can insinuate the
Thanks Bob,
Another good tip to add to my notebook! Unintended re-initialization can bring
disastrous consequences. This, I have discovered. Sigh.
Gregory
On Mon, Sep 12, 2011, at 1:00 PM, use-livecode-requ...@lists.runrev.com wrote:
> One of the things I do to prevent re-initialization
One of the things I do to prevent re-initialization of a card or stack is I
create a global, and upon successful initialization I set it to true. I check
it's value before initializing and only call the initialization handler if the
global is not set to true. This has the benefit of being able t
ges.
Craig Newman
-Original Message-
From: Gregory Lypny
To: use-livecode
Sent: Sun, Sep 11, 2011 10:44 am
Subject: Re: Question About PreOpenStack
Hi Craig,
I had posted this right (see below) after you in message 21. On reflection,
the
behaviour makes sense, and so does Mark
Hi Craig,
I had posted this right (see below) after you in message 21. On reflection,
the behaviour makes sense, and so does Mark’s suggestion that I move the main
stack’s OpenStack handler to the card script.
Gregory
> Hi Mark and Jacqueline,
>
> The substacks had PreOpenStack handlers that
Good stuff. Thank you, Mark. I’ll give that a shot.
Regards,
Gregory
On Sun, Sep 11, 2011, at 1:00 PM, use-livecode-requ...@lists.runrev.com wrote:
> Hi Gregory,
>
> Instead of putting an openStack handler in every substack, it is much easier
> to move the openStack in your main stack from
Hi Gregory,
Instead of putting an openStack handler in every substack, it is much easier to
move the openStack in your main stack from stack level to card level. If the
openStack handler is in a card script, it won't be triggered by opening a
substack.
--
Best regards,
Mark Schonewille
Econo
Hi Mark and Jacqueline,
The substacks had PreOpenStack handlers that called a library stack and
sometimes emptied out some fields, but what they did not have OpenStack
handlers. The absence of OpenStack handlers appears to have been the problem
because, after the the sub-stack executes its own
-Original Message-
From: J. Landman Gay
To: How to use LiveCode
Sent: Fri, Sep 9, 2011 8:48 pm
Subject: Re: Question About PreOpenStack
On 9/9/11 10:53 PM, Mark Wieder wrote:
> I went back and read the original posting. It's not clear to me that
> the preOpenStack han
On 9/9/11 10:53 PM, Mark Wieder wrote:
I went back and read the original posting. It's not clear to me that
the preOpenStack handler in the substack isn't firing, just that the
preOpenStack handler in the mainstack *is* firing.
I could be misremembering, as they say. Gregory can be the decide
Jacque-
Friday, September 9, 2011, 7:24:40 PM, you wrote:
> There has been some good info about how to block a preOpenStack handler
> from falling through to the mainstack, but I'm not sure that was the
> question. Gregory will have to verify, but as I understood it, he has a
> valid preOpenStack
There has been some good info about how to block a preOpenStack handler
from falling through to the mainstack, but I'm not sure that was the
question. Gregory will have to verify, but as I understood it, he has a
valid preOpenStack handler in a substack but it isn't executing.
Instead, he gets
Really?? I was under the impression that preOpenStack would not fire from the
first card because the stack was not open yet. You learn something new every
day!
Bob
On Sep 9, 2011, at 12:09 PM, Scott Rossi wrote:
> 3) move your preOpenStack handlers from the script of your mainstack into
> the
The other way of handling this is to have a mainstack that is really just a
splash stack + library, it doesn't even have to show itself on startup (put "on
preopenstack; hide this stack; end preopenstack" into the script of card 1 of
the mainstack). Then put whatever you want for preopenstack be
I always put empty preopenstack, openstack, preopencard,
and opencard handlers for my substacks. I also put in a closestack handler
in the substack that tells the substack to close. This seems like it should
just be a standard thing to do when making substacks. This will prevent any
stray messages
On 9/9/11 2:09 PM, Scott Rossi wrote:
Recently, Gregory Lypny wrote:
I have a main stack with a PreOpenStack handler and sub-stacks with
PreOpenStack handlers. Why is it that when I click a Go button in the main
stack that opens a sub-stack, the PreOpenStack handler in the main stack is
execut
Scott-
Friday, September 9, 2011, 12:09:57 PM, you wrote:
> 3) move your preOpenStack handlers from the script of your mainstack into
> the card script of the first card of your mainstack
Indeed, the documentation states that the preOpenStack message is
"sent to the destination card when you ope
Recently, Gregory Lypny wrote:
> I have a main stack with a PreOpenStack handler and sub-stacks with
> PreOpenStack handlers. Why is it that when I click a Go button in the main
> stack that opens a sub-stack, the PreOpenStack handler in the main stack is
> executed?
Messages from substacks auto
Hi Gregory,
That's called the message hierarchy. This is discussed in the user manual.
Messages go from front scripts to button/field to background, card, substack,
mainstack, stack in use to back scripts.
--
Kind regards,
Mark Schonewille
Economy-x-Talk
Http://economy-x-talk.com
Share the cl
Hi.
I don't see this. I made a main stack and a substack. When I open the subStack
from the mainStack, I only get an answer from the preOpenstack handler in the
subStack stack script.
I only get an answer from the PreOpenstack handler in the mainStack stack
script.
You are not passing "Pre
20 matches
Mail list logo
