[comp.sys.mac.hypercard] Bugs or not in HyperCard 1.2

lhe@sics.se (Lars-Henrik Eriksson) (08/30/89)

I just upgraded (finally) to HC 1.2. When reading a list of 1.1 bugs
that had been fixed in 1.2, I noticed that the behaviour on deletion
of cards had been changed.

According to the note, hypercard now doesn't send a closecard message
to the card being deleted and also doesn't send an opencard message to
the card becoming visible as a result of the deletion. I first thought
the documentation was in error, surely it must be the other way
around. When I tested, however, this was precisely the behaviour of HC
1.2.

Now I might accept that a card being deleted is not sent a closecard
message, but surely the next card should be sent an opencard message!
It should not matter to the next card whether it becomes the current
card because of a go command or because the previous card was deleted.

This behaviour is forcing me to rewrite several of my stacks.

Can someone from Apple please explain why HyperCard was changed in
this way.

Another HC 1.2 question: In some situations HyperCard 1.1 consistently
forgot to send a closefield message to an open field being closed.
This seems to have been fixed in 1.2. Can Apple confirm that
closefield is really always sent now. (In that case I can remove lots
of time-consuming workaround code from my stacks).

HC still sends an openfield message every time you click in a field,
even if the field was open before. This is very annoying if you use an
openfield handler to save the contents of the field before it was
opened. Is this behaviour intentional? Will it be changed (corrected?)
in future releases?
-- 
Lars-Henrik Eriksson				Internet: lhe@sics.se
Swedish Institute of Computer Science		Phone (intn'l): +46 8 752 15 09
Box 1263					Telefon (nat'l): 08 - 752 15 09
S-164 28  KISTA, SWEDEN