{#} Replies are directed back to [EMAIL PROTECTED]
{#} To reply to the author, write to "Steven W. Riggins" <[EMAIL PROTECTED]>
At 12:33 PM -0700 3/6/02, Colter Reed wrote:
>{#} Replies are directed back to [EMAIL PROTECTED]
>{#} To reply to the author, write to Colter Reed <[EMAIL PROTECTED]>
>
>On 3/6/02 12:16, "Mark H. Anbinder" <[EMAIL PROTECTED]> wrote:
>
>>> 2) Fire had no way (and still really doesn't) of knowing whether
>>> you were "active" in the window or if it just happened to be the
>>> front most window becuase you left it that way six hours ago.
>>
>> If you have a mechanism for determining that the user is idle so as
>> to share that information with the messaging servers, that could be a
>> plausible avenue to take in determining whether the user is likely to
>> be typing, right now, in the frontmost window.
>
>This would require checking (after *every* keystroke) how long it's been
>since the last key stroke. It's enough overhead, in the first attempt I
>made, that it lowered the speed at which I could type. (This might not be
>so much of an issue for someone who doesn't type 100 WPM.) And it's going
>to add to the CPU usage when Fire's idle.
>
>Even if we do attempt to detect "actively used" windows, there's still going
>to be the race condition where you start typing at the same time a new
>window pops up and you still end up typing in the wrong window.
So we just hack on it till we have an option to open new windows behind the frontmost
one :)
Steve
{#} ----------------------------------------------------+[ fire ]+---
