Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!helios!bcm!dimacs.rutgers.edu!seismo!uunet!lll-winken!sun-barr!apple!applelink.apple.com!maller From: maller@applelink.apple.com (Steve Maller) Newsgroups: comp.sys.mac.hypercard Subject: Re: Hypercard 2 problem with "on openstack" Message-ID: <11927@goofy.Apple.COM> Date: 31 Jan 91 19:44:53 GMT References: Sender: usenet@Apple.COM Distribution: na Organization: Apple Computer Lines: 24 In article rgonzal@elbereth.rutgers.edu (Ralph Gonzalez) writes: > 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 > start HyperCard by double-clicking on the Tmp stack. Its "on > openstack" handler is NOT invoked at all, and instead I get a "beep". The problem is that HyperCard encounters an "error" in trying to open the stack's resource fork and internally aborts the process of sending the "open" messages. This is because you probably left the file open inside of ResEdit. Did you expect this to work? The Mac's Resource Manager is *not* multi-user, so if someone has a file open for read and write permissions (as is normally the case), any other open requests will fail. -------------------------------------------------------------------- Steve Maller Disclaimer: I speak for neither my Software Commando employer or for Claris HyperCard Engineering Corporation. Apple Computer