<x-flowed>At 9:02 -0500 3/23/99, Paul J. Schinder wrote: > } If so, then I wonder if this could be a timing problem, with the > } app sometimes getting to the ARGV code before the AppleEvent has > } come in and set up @ARGV? But then how do MPW and the Finder manage > } to get it right? > > Timing problems are endemic in AppleScript. There's no way to > reliably control flow in AppleScript. MPW and the Finder seem to have > more control over the raw AppleEvents than AppleScript lets you have. An application *should* do only its "we'll do this stuff every time" initialization when it starts up, then wait for the first Apple event. That event will be oapp "you were started by double-clicking your icon" odoc "you were started by having these docs opened or dragged onto you" pdoc "you were started by having these docs printed" noop "none of the above: you're on your own" (or anything else another app in a suite of apps passes to LaunchApplication to be used as the initial Apple event...that's a matter of agreement among the applications involved). --John -- John Baxter jwblist@olympus.net Port Ludlow, WA, USA Give a man a fish and you feed him for a day. Teach him to fish, and you get rid of him for the weekend. ===== Want to unsubscribe from this list? ===== Send mail with body "unsubscribe" to macperl-request@macperl.org </x-flowed>