{#} Replies are directed back to [EMAIL PROTECTED]
{#} To reply to the author, write to Raphael Ho <[EMAIL PROTECTED]>
A slightly better technique would be detecting idleness using both window
focus and system idle.
The status should be set to idle if the system has been idle for x minutes
(therefore you have not typed anything) or Fire has lost window focus for x
minutes (therefore you cannot type anything)
Of course, in my case, you don't need any idle detection code. I'm just
plain idle. :-)
on 7/3/02 4:48 AM, Colter Reed at [EMAIL PROTECTED] wrote:
> {#} Replies are directed back to [EMAIL PROTECTED]
> {#} To reply to the author, write to Colter Reed <[EMAIL PROTECTED]>
>
> On 3/6/02 13:18, "Mark H. Anbinder" <[EMAIL PROTECTED]> wrote:
>
>>> This would require checking (after *every* keystroke) how long it's
>>> been since the last key stroke.
>>
>> OK, that's clearly not worthwhile. I really have no idea how these
>> clients decide whether you're idle or not. I seem to recall AIM using
>> someone else's extension at some point in the past, and of course
>> that's not an option for Fire.
>>
>> If you have no mechanism for keeping track of whether the user is
>> idle (and note that I'm talking about idle time, NOT whether the
>> user's actively typing in the frontmost window), then my suggestion
>> is irrelevant.
>
> Keeping track of how long the entire computer's been idle is easier. We
> already do that.
>
> I'm mulling the problem over in the back of my mind. I'll see if I can come
> up with something for a post-0.30.a version.
>
> Colter
>
>
> {#} ----------------------------------------------------+[ fire ]+---
>
_________________________________________________________
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
{#} ----------------------------------------------------+[ fire ]+---
