Xref: utzoo comp.sys.mac.hypercard:2981 comp.sys.mac.programmer:11736
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!cs.utexas.edu!uunet!munnari.oz.au!comp.vuw.ac.nz!kaukau.comp.vuw.ac.nz!waikato!ldo
From: ldo@waikato.ac.nz (Lawrence D'Oliveiro)
Newsgroups: comp.sys.mac.hypercard,comp.sys.mac.programmer
Subject: Re: Two (weird) HyperCard scripting problems; something to do with
Summary: HC has its message ordering screwed up
Keywords: HyperCard, message-passing
Message-ID: <1990Jan13.032824.10703@waikato.ac.nz>
Date: 13 Jan 90 03:28:24 GMT
References: <7056@tank.uchicago.edu>
Organization: University of Waikato, Hamilton, New Zealand
Lines: 21

I've come across similar behaviour myself, and I think I know what's
happening: HyperCard is going to the Home stack and invoking the
OpenStack handler there, *after* it's done the same for your stack!

There seem to be all kinds of problems with the order in which
HyperCard invokes various handlers. One case that's been bugging
me for a long time now is that, when I create a new card, the
OpenCard message is sent *before* the NewCard one! The way I
get around this is to check, in my OpenCard handler, if certain
important fields (which should have been initialised in NewCard)
are still empty; if so, OpenCard exits without doing anything.
Also, my NewCard handler ends with an explicit call to OpenCard.

Yuk.

All I can suggest is, stick a few "Answer" statements inside various
handlers to help you determine the order in which HyperCard is
calling them; once you've done that, *then* you can sit down and
figure out what to do about it.

Lawrence