Hi again.

In TODO on epicsol.org there are noted some "windows issues"
(i cannot connect there right now to quote exactly)

Since it is close related to servergroups, i wonder
what exactly those issues are.
However, at my taste, the windows handling is actually awfull, 
even w/out server groups.

I also slightly cannod get purpose of having
bound channel, default channel, waiting channel, bound queries.

My suggestions are:
- generalize 'source/target', as an substance to describe
  whom and how to send messages and what to log.
  structure should have something like:
  server group, current server, 
  actual target (nick or chan), 
  refcount (number of windows associated)
  /* DCC connections should fit here somehow too */
  
- associate each window with list of targets (displaying from),
  having one target current (sending to).
  += command next_target to cycle curret betwean them
  
- when deciding where to display message,
  compare targets of windows instead of servers or whatever

- on disconnect, clear 'server' field in all associated targets
- on [re]connect, put new server in targets with matching
  servergroup and NULL server field.
  (nothing to do with windows)

There questionable possibility of having unattached
targets, like currently - there possible to be joined on channel,
but having no windows associated.

IMHO: 
- when window is closed, all targets associated should be deleted
  (or unrefcounted), and if no target associated with some server left,
  disconnect from it.


Seems like EOF

qMax
_______________________________________________
List mailing list
[EMAIL PROTECTED]
http://epicsol.org/mailman/listinfo/list

Reply via email to