Mea Culpa: FlexTime Scripted Cues
September 15th, 2006FlexTime has a major flaw in it where references to AppleScripts are not reliably saved/restored in routine documents. I’ve fixed the problem but it actually required quite a bit of change to my scripting code. So… I’m both embarrassed about the bug and nervous about the changes. Rather than release an update and hope for the best over the weekend, I thought I’d float a beta build.
If you’re using FlexTime’s scripted cues and can’t seem to figure out why the script isn’t running reliably, don’t feel stupid, it’s not your fault! Please do me the favor of downloading FlexTime 1.0.4b1. You’ll find the scripting experience much less frustrating.
Assuming I don’t hear any negative feedback, I’ll be releasing a final 1.0.4 build next week, so this problem won’t bite too many more people.
Update: I released FlexTime 1.0.4 today (September 20, 2006) with no changes from the beta (aside from the version string).
September 16th, 2006 at 4:34 pm
A bigger display of the relative time passed in the activity would be awesome.
September 17th, 2006 at 9:11 pm
1.0.4b1 seems to remember the script for me. I created a new routine that ran a time left script.
Ran it. Saved it. Closed the FlexTime. Opened FlexTime. Started the previously created routine.
It found and executed the time left script.