> his licq is running at home, always. > and when he's at work and want to write a short message to someone, he > "grabs" the UIN from his running licq at home by connecting from his desk at > work. he writes his message and short time later he can be sure that his > home-licq is up and running again.
> this is the only useful case i can think of. That's exactly how I use it. I agree it would be annoying if you wanted to use the work LICQ for an extended period of time, but if you only need it for a minute or two it's much easier knowing that the home LICQ will reconnect automatically. I do think it would be worth making it an option though, it seems that there are enough people wanting both behaviours. Unless of course you can work out a way to communicate between the LICQ clients, so that the home LICQ won't reconnect until the work LICQ is offline...? Cheers, Adam. ------------------------------------------------------- This SF.net email is sponsored by: Perforce Software. Perforce is the Fast Software Configuration Management System offering advanced branching capabilities and atomic changes on 50+ platforms. Free Eval! http://www.perforce.com/perforce/loadprog.html _______________________________________________ Licq-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/licq-devel
