Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!know!zaphod.mps.ohio-state.edu!rpi!julius.cs.uiuc.edu!apple!bc From: bc@Apple.COM (bill coderre) Newsgroups: comp.sys.mac.hypercard Subject: Re: messages to other stacks Message-ID: <44786@apple.Apple.COM> Date: 13 Sep 90 19:35:29 GMT References: <44723@apple.Apple.COM> <90256.124659DN5@psuvm.psu.edu> Distribution: na Organization: private consultant for hire Lines: 36 D. Jay Newman: |Sorry, but you can use parameters with SEND. |The line | send "DoMenu Quit HyperCard" to HyperCard |works fine. Touche. My language was insufficiently precise. But let's look at the fully-precise specification, shall we? send to destination may be any HC object in the current stack -- cd, btn, fld, bg, stack, Hypercard -- or to another stack as an entity. You can also send to "me," "the target," and, in 2.0, an "xwindoid." send-message contains a message name -- either a system message or the name of an "on" handler, and may contain parameters. (ie. "MyHandler 5,6,foo", "openCard"). It may NOT contain a function call (ie. "MyFunction(5)" will fail). You can certainly send to a handler that calls a function, though. send is considered a "keyword" in Hypertalk, which means that it does not change "it" or "the result." It also does not actually "go" to the location of the object specified, so it does not send "openCard", etc. Its function is to inject the specified message into the message order at the object specified, so if that particular object cannot handle the message, it flows up the message-routing in effect at the time, until it hits Hypercard, which will conveniently discard system messages and complain about other messages. OK? bill coderre all this info is published in Winkler & Kamins, and as such does not constitute release of confidential information.