{#} Replies are directed back to [EMAIL PROTECTED]
{#} To reply to the author, write to Colter Reed <[EMAIL PROTECTED]>
On 3/29/02 15:18, "Jeff Leung" <[EMAIL PROTECTED]> wrote:
> Yes, I understand what the phrase means, and I do remember this being
> discussed maybe a month ago.
>
> So there currently is no way to have new windows created without them being
> key. Has it always been this way?
Yes, it's always been this way. People just didn't notice anything until
they thought thought the preference was broken.
> Is it something that is difficult to fix, or has there just been too much
> other stuff to do such that no one's gotten around to it? If so, I can try
> to muck with it myself.
The problem is deciding when a new chat window should be brought to the
front and when a new chat window should be brought in as the second window.
What I'm going to try is checking whether the current key chat window is
being actively used -- something's been typed in the last two seconds or so
-- and not obscuring an active window like that. I'm adding the code for
seeing how long it's been since a window has been used as part of the MSN
"I'm Typing" notifications. Once that's in place, it should be rather
straightforward to tell when a chat window shouldn't be interrupted.
Until then, there's not much that can be done about the problem. The other
option is to automatically make *every* new chat window come in behind the
front-most chat window, which isn't a good idea.
And before someone suggests it, yes, I'm mulling over the possibility of
allowing (as a preference) the ICQ style of not opening the incoming message
window until the user asks for it.
Colter
{#} ----------------------------------------------------+[ fire ]+---
