==start script sample (line wrapping alert!)
-- first of all, put into an otherwise unused script:
on mouseMove
send resetLogout to stack chinpr
pass mouseMove
end mouseMove
on rawKeyDown
send resetLogout to stack chinpr
pass rawKeyDown
end rawKeyDown
-- then I put
send logoutMessage to me in 300 seconds
If the machine goes to sleep before the 300 seconds are over this
doesn't wake it up, right?
I once tried using this send trick for time critical stuff, but
that doesn't work if the machine goes to sleep. What's more, I get
the impression that after the
On Sunday, August 17, 2003, at 09:02 AM, Victor Eijkhout wrote:
I once tried using this send trick for time critical stuff, but that
doesn't work if the machine goes to sleep.
I wonder what is a good way to make sure there is a wake up. Or if
there is one. Or how to prevent sleep.
What's
I once tried using this send trick for time critical stuff, but
that doesn't work if the machine goes to sleep.
I wonder what is a good way to make sure there is a wake up. Or if
there is one.
There must be, though system dependent. I've seen an mp3 alarm clock
which could wake up my Mac to
I should probably point out at this point, I did not mention using a
frontscri[t because I am a callow youth, and forgot to mention that that was
the proper way to implement this.
All Hail Sarah -- Who deserves i!
Oh...and Dar. Who does to...I guess. :)
- Original Message -
From: Dar
On Friday, August 15, 2003, at 02:23 PM, Devin Asay wrote:
on openStack
-- start timeout counter
insert the script of image PRbg1.jpg into front
Cool idea!
send logoutQuery to stack chinpr in 5 * 60 seconds -- or
whatever time you want
Replace above line with this:
resetLogout
end
On Friday, August 15, 2003, at 02:23 PM, Devin Asay wrote:
It seems okay until you start examining the pendingMessages. For some
reason the sent messages start queuing up rapidly
Even those experts see this. In design review and in testing always
watch for this. Always. Always.
I check for
I want to write a routine in my stack that will automatically log the
user out after X minutes of inactivity, in the same way the screen
saver will kick in after X minutes. Any mouse or keyboard event would
reset the timer. I've been playing with the idle handler like this:
global startSeconds
On Thursday, August 14, 2003, at 03:46 PM, Devin Asay wrote:
The problem with this approach of course is there is no way to reset
the startSeconds unless the timeOut handler runs. I don't want to have
to trap every single mouse and keyboard event to reset startSeconds.
Perhaps you can put a few
Understand that I have not given this even the slightest bit of thought before
posting, but I think you are going to be better off using send to do this.
What you are going to want to do is something like this...
global gGoToSleep
on startup
send timeout in 5X60 seconds --for a 5 minute time
10 matches
Mail list logo
