Locking Messages

Bridger Maxwell bridgeyman at gmail.com
Sat Mar 4 12:57:53 EST 2006

  Sorry I wasn't very clear on my question.  I have made a stack (Stack 1)
that copies a card from any stack running in the background (Stack 3),
pastes it on another stack that was just made (Stack 2), and sends stack 2
over the network where the card that was added to any stack that intercepts
it.  It is made to be able to add any card to any stack.  The thing is a
card may have a handler in it that is triggered, that refers to an object on
another card.  Because it has been seperated from the rest of the stack, it
can't find that object and it causes errors.  Once it is inserted into the
new stack it should stop causing errors, but until then I need to lock the
messages to the stack holding the card so it doesn't trigger anything.  I
can't really predict what handlers will be triggered, or what the errors are
going to be so I can't just intercept them beforehand.  Any ideas?

On 3/4/06, Rob Cozens <rcozens at pon.net> wrote:
> Hi Bridger,
> > I have a stack (Which I will call Stack 1) that
> > makes another stack (I will call it Stack 2), copies a card from some
> > other stack running in the background (which I call Stack 3) and sends
> > the new stack with the copied card all over the network where it is
> > added to whatever stack sees it.  The problem is that sometimes the
> > card on Stack 2 has unexpected handler in it that cause random errors
> > when I am working with it.  I realize I can lock the messages, but
> > that locks the messages for the Stack 1 also, which I cannot do.  Is
> > there any way of keeping messages from being passed to Stack 2,
> > without locking the messages from Stack 1?
> >
> I am not sure exactly what you are describing.
> If Stack 2 is created on-the-fly, where does the "unexpected" handler
> come from?  The card copied from Stack 3?
> Do you have handlers with identical names in Stack 1 and 2?
> If Stacks 1, 2, & 3 are all your creations, you should be able to avoid
> any duplication.
> If the error is caused by broadcasting a message (eg: doWhatever),
> perhaps the problem can be avoided by directing the message to the
> correct object (eg: send "doWhatever" to card 1 of stack "Stack 1").
> Rob Cozens
> CCW, Serendipity Software Company
> "And I, which was two fooles, do so grow three;
> Who are a little wise, the best fooles bee."
> from "The Triple Foole" by John Donne (1572-1631)
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution

More information about the Use-livecode mailing list