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.hypercard Subject: Hypercard 2 problem with "on openstack" Keywords: hypercard 2 Message-ID: Date: 31 Jan 91 13:56:25 GMT Distribution: na Organization: Rutgers Univ., New Brunswick, N.J. Lines: 23 I have the following problem with HyperCard 2 which is either a bug or a misunderstanding on my part. I haven't kept up with this newsgroup so forgive me if it has already come up. 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 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. (Of course I can get around the problem by writing an "on startup" handler, but this seems like the wrong solution...) 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)