{#} Replies are directed back to [EMAIL PROTECTED]
{#} To reply to the author, write to "Mark H. Anbinder" <[EMAIL PROTECTED]>
When Fire 0.31.a puts up a dialog box, such as the knock-knock dialog
for an incoming message from an unknown user, it ceases to be able to
handle tasks.
I suspect this means the user causing the knock-knock doesn't get the
current away message. I'm SURE it means subsequent incoming messages
from other users, including users for whom I already have an open
conversation, don't get the current away message.
Once the user has dismissed the knock-knock dialog, Fire proceeds to
process, excruciatingly slowly and in sequence, all queued up
activity. That includes a parade of buddies coming and going,
incoming messages appearing, etc.
This happened to me last night at home, and just now at work while I
was out to lunch. Especially at work, it's fairly important that away
messages keep working, so my colleagues can get a response and know
that I'm not simply ignoring them.
I'd suggest a less-modal approach. The application really shouldn't
put itself in a state where it can't respond with away messages or
keep the buddy list accurate.
How about, if a message comes in from an unknown IMer, display a
message window for that IMer and then open a knock-knock "sheet"
within that window. (Don't display the message text until the user
has accepted it.) That should allow activity in other windows to
continue.
--------------------------------------------------------------------------
Mark H. Anbinder [EMAIL PROTECTED] - 607-255-8634
Macintosh Specialist 120 Maple Avenue 136K Ithaca NY 14853
Senior Technical Consultant
Cornell University http://www.cit.cornell.edu/staff/mha1/
--------------------------------------------------------------------------
{#} ----------------------------------------------------+[ fire ]+---
