Xref: utzoo comp.sys.mac.hypercard:2940 comp.sys.mac.programmer:11601
Path: utzoo!utgpu!jarvis.csri.toronto.edu!clyde.concordia.ca!uunet!samsung!brutus.cs.uiuc.edu!ux1.cso.uiuc.edu!tank!gft_robert@gsbacd.uchicago.edu
From: gft_robert@gsbacd.uchicago.edu
Newsgroups: comp.sys.mac.hypercard,comp.sys.mac.programmer
Subject: Two (weird) HyperCard scripting problems; something to do with
Message-ID: <7056@tank.uchicago.edu>
Date: 8 Jan 90 20:19:56 GMT
Sender: news@tank.uchicago.edu
Lines: 31

Date:  8 JAN 90 14:15:23    
Organization:  University of Chicago Graduate School of Business
-----------

I'm writing a moderately complicated stack and I've run into a strange problem:
my stack behaves differently when it's started up by itself (that is, when the
stack itself is double-clicked) than when it's launched once one is already in
HyperCard.

Specifically, in my openStack handler, I set userModify to TRUE (this will
eventually be running off a write-protected server) and I click in a particular
field so that the user can immediately enter data.  This works find if I launch
the stack from within HyperCard or if I move to it from another stack.  But if
I launch the stack itself from the Finder, things _seem_ to get set up right
(the I-bar appears in the proper field and userModify is set right), but right
after openStack there's a bit of disk-trashing, and my I-bar disappears and
userModify is set back to FALSE.

Yo no comprendo.  What could be executing after openStack?  I checked the home
card for the startUp handler, but it didn't really seem to contain anything
that would cause this.  What am I missing?

Any info appreciated!

Robert
 
============================================================================
= gft_robert@gsbacd.uchicago.edu * generic disclaimer: * "It's more fun to =
=            		         * all my opinions are *  compute"         =
=                                * mine                *  -Kraftwerk       =
============================================================================