zameericle
Registered
hello,
I have decided to embark on creating my own alarm clock (ya I know it already exists)...
Anyhow.. I am trying to create iCal like functionality whereby when you quit my App, the timer events will still be active.
My idea is the following (I was hoping someone could offer any comments):
(1) Create an Applescript that creates a timer from the given input (namely, the time to go off and the action) - let's call this the Timer-script.
(2) use applescript from my App to tell the finder to execute the Timer-Script
now where I am confused is this: If I told the finder to execute Timer-script, is Timer-script considered a sub-process of my App - therefore if I quit my App, Timer-script quits as well? or will I see the execpected behavior - my App quits but Timer-script continues?
any comments would be great.
thanks
Zameer
I have decided to embark on creating my own alarm clock (ya I know it already exists)...
Anyhow.. I am trying to create iCal like functionality whereby when you quit my App, the timer events will still be active.
My idea is the following (I was hoping someone could offer any comments):
(1) Create an Applescript that creates a timer from the given input (namely, the time to go off and the action) - let's call this the Timer-script.
(2) use applescript from my App to tell the finder to execute the Timer-Script
now where I am confused is this: If I told the finder to execute Timer-script, is Timer-script considered a sub-process of my App - therefore if I quit my App, Timer-script quits as well? or will I see the execpected behavior - my App quits but Timer-script continues?
any comments would be great.
thanks
Zameer