pass

[xbury.cs at clearstream.com]

Hi Lars,

Pass this simply sends the event up the event queue. 
So if you have an opencard hander in a card, an opencard handler in the 
stack
script, the pass Opencard will "pass" the message to the stack. If you 
include
it, it will not be passed.

it's usually a good idea to pass the hyperCard events back up. Any plugin
or stack in use may depend on this event being passed also.

To skip the event:
on opencard
  answer "do it?" with "Abort" or "no" or "OK"
   if it is Abort then exit opencard -- skip - no passing
 if it is No then pass opencard -- skip - and pass the event
 do it
  pass opencard
end opencard
Hope that helps.

cheers
Xavier

On 07/06/2005 12:05:56 use-revolution-bounces wrote:
>hi all!
>
>I am having a novices problem grasping the "pass" control structure.
>Let's say i have a stack with a preOpenCard handler, but I want to
>run through the stack and want to skip the preOpenCard.
>
>stack script:
>
>on preOpenCard
>do this
>do that
>etc.
>
>
>but another script:
>
>repeat x times
>go next
>do this
>do that
>
>and I want to skip the preOpenCard handler.  Is "pass preOpenCard"
>the way to do this, and if so, where the heck does it go?
>
>Cheers,
>
>Lars
>_______________________________________________
>use-revolution mailing list
>use-revolution at lists.runrev.com
>http://lists.runrev.com/mailman/listinfo/use-revolution


-----------------------------------------
Visit us at http://www.clearstream.com
                                                          
IMPORTANT MESSAGE

Internet communications are not secure and therefore Clearstream
International does not accept legal responsibility for the contents of
this message.

The information contained in this e-mail is confidential and may be
legally privileged. It is intended solely for the addressee. If you are
not the intended recipient, any disclosure, copying, distribution or
any action taken or omitted to be taken in reliance on it, is
prohibited and may be unlawful. Any views expressed in this e-mail are
those of the individual sender, except where the sender specifically
states them to be the views of Clearstream International or of any of
its affiliates or subsidiaries.

END OF DISCLAIMER