{#} Replies are directed back to [EMAIL PROTECTED]
{#} To reply to the author, write to "Steven W. Riggins" <[EMAIL PROTECTED]>
>{#} Replies are directed back to [EMAIL PROTECTED]
>{#} To reply to the author, write to Colter Reed <[EMAIL PROTECTED]>
>
>On 2/11/02 13:51, "Steven W. Riggins" <[EMAIL PROTECTED]> wrote:
>
> > Um I think my point was that fire should not:
>>
>> a) Keep reconnecting ad nauseum on a blocked error, even if I have reconnect
>> checked
>> b) Should not open 1000 dialogs on top of each other in any case (should have
>> a better UI for this)
>
>Yes, that's all fine and good, but I'd rather focus my time on preventing a
>problem in the first place instead of making the symptom look pretty. Would
>you rather have Fire notify you that you've been blocked more gracefully or
>would you rather not get blocked in the first place?
>
Well both have to be resolved at some point. One time this happened by signing off
Fire, launching AIM to send a file, then quitting and going back to Fire.
Blocked.
Darn fast OS X, hehe.
It could not have blocked, yes. Esp since I chose connect while i was connected. So
where Fire can prevent it, that would be good.
Steve
{#} ----------------------------------------------------+[ fire ]+---
