Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!bcm!dimacs.rutgers.edu!rutgers!elbereth.rutgers.edu!rgonzal
From: rgonzal@elbereth.rutgers.edu (Ralph Gonzalez)
Newsgroups: comp.sys.mac.programmer
Subject: HyperCard 2 problem with "on openstack"
Keywords: hypercard
Message-ID: <Feb.5.11.20.34.1991.29288@elbereth.rutgers.edu>
Date: 5 Feb 91 16:20:36 GMT
Distribution: na
Organization: Rutgers Univ., New Brunswick, N.J.
Lines: 28



I have the following problem with HyperCard 2 which is either a bug or
a misunderstanding on my part.  

First I open a resouce fork in a new Hypercard 2 stack called "Tmp"
using ResEdit.  I add a "vers" resouce, or no resource at all.  Then I
quit ResEdit and start HyperCard by double-clicking on the Tmp stack.  Its "on
openstack" handler is NOT invoked at all, and instead I get a "beep".
If, on the other hand, I start HyperCard by double-clicking on
HyperCArd or Home, and THEN open Tmp, then its openstack handler works
fine.  WHY IS THIS?  I don't get this problem if I never open a
resource fork for the Tmp stack.

I can get around the problem by writing an "on startup" handler, but
it seems like there should be a better solution:

    on startup
        pass startup
    end startup

I also tried Apple's Resource Mover in the new Power Tools stack, but
it tends to bomb out on me - anyone else have this problem?

Thanks to anyone who responds,
Ralph
(rgonzal@chowder.rutgers.edu or rgonzal@elbereth.rutgers.edu if it
bounces)