• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Dual Purpose Applet Question
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Dual Purpose Applet Question


  • Subject: Re: Dual Purpose Applet Question
  • From: John W Baxter <email@hidden>
  • Date: Tue, 5 Dec 2000 16:48:34 -0800

At 17:49 -0500 12/5/00, email@hidden wrote:
>If the applet was "stay open", and you double click on it after it is running,
>it doesn't get sent a "run" event.
>
>The solution is to provide a "reopen" handler
>
>on reopen
> beep 3
>end reopen
>
>The initialization logic in complex programs can get tricky, because you
>may get
>"reopen" after an "open", or you may get it after a "run". But in your case,
>you probably can just make the "reopen" handler just call "run".

There was an older version of FileMaker (before the reopen event was
created) which tried to implement "if you get a run (oapp) message when you
have been running, ignore it" by removing the oapp event handler. But it
botched the removal, and so responded to oapp events in mid-run by doing
its initial oapp event stuff again.

The reopen way is better. ;-)

--John
--
John Baxter email@hidden Port Ludlow, WA, USA


References: 
 >Re: Dual Purpose Applet Question (From: email@hidden)

  • Prev by Date: Re: Should be a simple script
  • Next by Date: Re: Finder's open event has properties? Cal?
  • Previous by thread: Re: Dual Purpose Applet Question
  • Next by thread: Re: Dual Purpose Applet Question
  • Index(es):
    • Date
    • Thread