I'm trying to schedule something to happen some time in the future. Due
to some other complexities, I cannot just do a
send mouseUp to me in 1000 seconds
Rather, I have to wake up every 10 seconds and figure out whether it is
time to do the processing or not. The current code is presented
Jon wrote:
I'm trying to schedule something to happen some time in the future.
Due to some other complexities, I cannot just do a
send mouseUp to me in 1000 seconds
Rather, I have to wake up every 10 seconds and figure out whether it
is time to do the processing or not. The current code
Alex Tweedly wrote:
local nextFTPTime
on mouseUp
if the seconds nextFTPTime then
do ftp Stuff
put the seconds + field TestFreq into nextFTPTime
end if
send mouseUp to me in 10 seconds
end mouseUp
You might want to make that
send mouseUp to me in min(10, nextFTPTime-the
Jon,
I should have pointed out in my previous response that the way to
find these problems in the future is to use the RR debugger. If you
set a break point at the line:
if currTime mostRecentFTPTime then...
and if you open the Variable watcher you would see that the
variable
Jim:
I do, in fact, use the debugger. I also write lots of debugging
information out to the log I'm creating. The code I stripped out of the
example was exactly all of that debugging code.
:)
Jon
Jim Hurley wrote:
Jon,
I should have pointed out in my previous response that the way to
Alex Tweedly wrote:
snip
2. Unless you need to for some reason I don't see here, don't mess
around with date time.
What I'm trying to do is find a way to express more than 60 minutes
after the most recent time/date stamp in such a way that it will not
fail across noon/midnight
If it helps, 'the seconds' (like 'the time', 'the date', 'the files')
is really a function, and can be used like: put seconds() into tNow.
Incidentally, looking this up reveals that the dictionary also lists
'seconds' (plural) as a keyword to denote the second member of a set,
when obviously
Mark Smith wrote:
If it helps, 'the seconds' (like 'the time', 'the date', 'the files') is
really a function, and can be used like: put seconds() into tNow.
If you're prone to curmudgeonly habits you might find the function form
very useful when skimming code to help differentiate from
Bug 3066 entered
On 19 Aug 2005, at 21:25, Richard Gaskin wrote:
Mark Smith wrote:
If it helps, 'the seconds' (like 'the time', 'the date', 'the files')
is really a function, and can be used like: put seconds() into tNow.
If you're prone to curmudgeonly habits you might find the
Jon wrote:
Alex Tweedly wrote:
snip
2. Unless you need to for some reason I don't see here, don't mess
around with date time.
What I'm trying to do is find a way to express more than 60 minutes
after the most recent time/date stamp in such a way that it will not
fail across
10 matches
Mail list logo
