Thank you for the feature in #141, @karbassi. 馃挍
A proposal to change the API default:
timer://5 per default does this if a timer is already running.... it starts a new timer, rather than updating the existing one. Should the timer of window 1 be set to 0, then it reuses that timer, as it currently does.
Otherwise, even with this change, if we want to have multiple timers, we need to write custom AppleScript to check if a timer already is running, and if so, then (1) run timer://new and keep track of what window number <w> it is... and (2) run timer://<duration>?window=<w>. With a slight modification of the API, no need for custom coding is needed.
I hope what I write makes sense.
Thank you for the feature in #141, @karbassi. 馃挍
A proposal to change the API default:
timer://5per default does this if a timer is already running.... it starts a new timer, rather than updating the existing one. Should the timer of window 1 be set to 0, then it reuses that timer, as it currently does.Otherwise, even with this change, if we want to have multiple timers, we need to write custom AppleScript to check if a timer already is running, and if so, then (1) run
timer://newand keep track of what window number<w>it is... and (2) runtimer://<duration>?window=<w>. With a slight modification of the API, no need for custom coding is needed.I hope what I write makes sense.