With a later release of DtP came an extended/improved version of the built-in script and this custom script has at some point stopped working for me too.
What I loved with the custom script was the option to type in an absolute date.
Over here on 10.7.2, when v009 is executed from DTPO (2.3.1.1) the first window prompting for the date will appear, but the second window prompting for text does not and no reminder is created in OF. If I execute the script from ScriptDebugger, both windows open and the OF reminder is created. I don’t see anything in the ScriptDebugger logs to indicate problems.
Same here on OS10.6.8 with OF1.9.4. Started with ScriptEditor it works, started from DtPO’s menu it doesn’t. My OS runs in English, so I can exlude an issue with localizations.
And - only when started from DtPO’s menu - when I type an absolute date, I receive “unable to parse 06/12/2011 as a date”. “06.12.2011” or using “11” instead of “2011” doesn’t work either.
Kind regards,
Bernd
PS: Excuse me getting off topic, but I like how korm is walking the grass on the new board.
Sorry, Robin, over here v010 acts the same as v009 – the first dialog is displayed; the second is not displayed; an OF task is not created. Though it works fine with ScriptDebugger.
Seems to be something to do with the calls to System Events. Perhaps if you displayed the dialogs without calling System Events? Perhaps DTPO isn’t playing nicely with System Events?
(The only use of application id “sevs” which can’t, I think, be removed, is the pasting keystroke – the others do look redundant because they are already bracketed by application id “DNtp” – they are a simply a reflex to cope with the fact that some script run environments, Keyboard Maestro in particular, can’t cope with raw calls to functions like display dialog)
Still the same, v011 behaves like the older ones here: It starts with the first screen and after I confirm, nothing happens: No second window, no To Do in OF.
Also I still get “unable to parse 20.12.2011 as a date”.
When I run v011 from the ScriptEditor all works as it should and also absolute dates are accepted.
Something happening when the script is started from DT’s script menu seems to be preventing the correct routine.