There are two problems here. The first is the incompatibility between
MetaCard and HypeCard WRT openCard and openStack handlers (in
MetaCard, these handlers are executed in parallel with the window
manager managing the window, so you can't count on being able to see
the results of the script until *after* the script is finished).
The second, and this is a classic HyperCard programming mistake, is
that by using openCard handlers you're forcing another level of
recursion for each new card that is opened. In HyperCard, this
process stops after about 30 cards with an recursion depth error,
whereas in MetaCard the process continues until you use up all your
swap, causing the machine to slow down to a crawl.
The better solution is to put an idle handler in the stack script, and
check "the seconds" to see if it's time to go to a new card (save the
start time in a global variable). See the "Audio Demo" stack for an
example of this technique.
> Can i see the script of a card with the above event in the scipt directly
> (that means without opening the card)?
I'm not sure I understand the question, but the answer might be yes,
using the Message Box:
edit the script of card "whatever" of stack "some stack"
> Thanks
> Frank Bachmann, Email: bachmann@gmd.de
> Gesellschaft fur Mathematik und Datenverarbeitung mbH (GMD)
> German National Research Center for Computer Science
> Forschungsbereich Mensch-Maschine-Kommunikation (MMK)
> Schloss Birlinghoven, Postfach 1316, D-53731 St.Augustin
>
>
-- *********************************************************************** * Scott Raney 303-447-3936 Remember: the better you look, * * raney@metacard.com the more you'll see -- Lidia * ***********************************************************************