{#} Replies are directed back to [EMAIL PROTECTED]
{#} To reply to the author, write to Jason Townsend <[EMAIL PROTECTED]>
On Tuesday, May 14, 2002, at 09:57 PM, David Thorp wrote:
> I'm not a TOT user. But there are some things in 0.30b that I've come
> accross, that may not have been addressed in TOT yet. Sorry if these
> aren't
> helpful, but maybe one or two of them are:
We appreciate the feedback on what everyone's top issues are with
Fire... however, I think Eric was interested in any really bad problems
with TOT CVS builds that may not be in .30b. That said, I'll try to
respond to your comments.
> 1. If I have my connections set up to auto-login, but I am not
> connected to
> the internet (but maybe I'm opening Fire to check out a previous
> conversation or something) ICQ in particular (and possibly others)
> insist on
> continuing to try to connect, no matter what I do to try to persuade it
> otherwise (including OK'ing the message and choosing disconnect all
> from the
> menu). The only way it seems I can stop the messages continually
> popping up
> is to go into accounts, turn off the auto login for ICQ, then quit and
> restart Fire. At which point I have to then turn it back on again for
> next
> time and so on. A couple of others have mentioned issues like this
> (eg. war
> between two Fire's trying to connect at once) so I thought I'd mention
> this
> in case it's related.
I'd like to make Fire more tolerant of network transitions and bad
network connections. There are three things to do for this:
1) Make Fire multithreaded. This would allow connecting to different
accounts in parallel instead of in series. Especially helpful if you
have 6 accounts like me.
2) Test for connectivity before attempting a connection. This would help
in the case that Fire tries to connect when there's no network available.
3) As has been suggested a couple times, wait a while before a reconnect
on wake. I'm thinking 20-30 seconds should do it.
From the standpoint of what is realistic to do soon, #3 is probably the
first one to implement and #2 is the next candidate. I'm not going to
promise that either of these will be in .31a, however. #1 is a pretty
major architectural change and will require a lot of changes to make all
the threads play nicely together.
> 2. Don't know if this is a bug or a feature: My buddy list insists on
> recreating the "Family", "Co-Workers", and "Buddies" groups in the setup
> lists tab, despite no-one being in those groups, and me repeatedly
> deleting
> them.
I fixed this a while back... will be in .31.a. These are probably coming
from your AIM server buddylist.
> 3. Blocked buddies in MSN still seem to be able to see me and send me
> messages occasionally. this might be an issue with Yahoo and AIM as
> well,
> but I'm not certain of that. This is despite the fact that I have
> unblocked
> and re-blocked them using the contextual menu (as opposed to just
> dragging
> them in and out of the blocked buddies group).
Haven't heard of this before.
> 4. Can't delete or change Yahoo buddies. Well, I can change them, but
> it
> just creates a new one for the change, and keeps the old one there as
> well.
> There seems to be no way of removing them in Fire. (I remember this was
> raised once before and the answer was to remove from within the Yahoo
> client
> so that the server removes them, but I'm kind of thinking that a way of
> doing it in Fire would be ideal right?) I am not certain but I think
> this
> is an issue with AIM buddies as well.
This probably means it is coming back from the server side buddy list.
We really need a notification to be sent to the service when changing a
buddy's name or group so that we can properly delete the old and add the
new, and block or unblock as appropriate.
> 5a. It may be that you've addressed this (judging by some of the
> correspondence about TOT) but in AIM, Yahoo and MSN at least, font
> settings
> and sometimes colour settings made at my end, are not reflected in my
> buddies' windows using the standard AIM, Yahoo and MSN clients.
I just checked in support for sending formatting information (font,
color, bold, etc.) on Yahoo. I think AIM already works in .30.b. What
client is not working with AIM sending style information?
MSN doesn't send style information currently, and I don't expect this to
change for .31.a.
> 5b. In some cases, the settings that they set aren't reflected at my end
> either. With this one (5b) I think AIM is ok, while Yahoo colours work
> but
> fonts don't, and MSN nothing works I think.
I noticed some problems with the Yahoo parser in implementing the
support for sending formatting. I've improved this somewhat but there
are still some issues with it. MSN does not support formatting on
incoming messages currently.
> 6. Also, on fonts and colours - Have I missed something or is there no
> way
> to set a default text colour for outgoing messages? I can set a default
> font, but colours won't stick. For example, I want my text to always be
> Futura, 12 point and dark teal in colour. The futura 12 point thing
> always
> works, but I always have to set it to the colour I want whenever I
> open a
> new window. Seems inconsistent to me, but maybe there's a good reason
> for
> this.
Sounds like a good feature request. This sort of thing will make a lot
more sense when we support styled messages across more services.
> 7. MSN group chats pleeeeaase. I guess this must be a tricky one or
> something, and sorry if you've addresses this in TOT. I really think
> this
> is important, because it's just impossible to follow conversations when
> others invite you into a group chat but it's popping up in many
> different
> windows (one separate window for each person in the group chat).
> Basically
> using Fire I just can't participate in these, and that's a bit of a
> bummer.
This requires that we keep track of an MSN switchboard for each open
window, which unfortunately is a nontrivial change. When we fix this we
will send typing notifications as well. Don't think this will be in
.31.a.
-Jason
--
Have a question? Have you read my Fire Frequently Asked Questions?
<http://homepage.mac.com/townsend/programs/fire.html>
{#} ----------------------------------------------------+[ fire ]+---
