Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!van-bc!rsoft!mindlink!a347
From: John_Miller@mindlink.UUCP (John Miller)
Newsgroups: comp.sys.mac.hypercard
Subject: Re: does HC 1.2.5 work on locked disk?
Message-ID: <4761@mindlink.UUCP>
Date: 11 Feb 91 12:49:43 GMT
Organization: MIND LINK! - British Columbia, Canada
Lines: 18

> 2) If you need to use the userModify property, you have
>    to trap it in both the openStack and startup handlers.
>    The startup handler should send the startup message
>    to the Home stack and then set the userModify property.
>    If you don't do this, you stack will not work if it is
>    the startup stack.  This is related to the
>    startUp/openstack message sequencing problem in 1.2.x.

To clarify this a bit, the userModify property is a
global property that is reset each time a new stack
is opened.  The messaging sequence in HyperCard 1.2.5
sends the openStack message before the startup message.
Your openStack handler can set the userModify, but the
standard HyperCard startUp handler jumps to the preferences
card (with locked screen) and then jumps back.  This
switching between stacks resets the userModify property.
The standard startUp handler does not restore the userModify
value.