[Konversation-devel] [Bug 137074] Don't close channel tabs on non-user-induced PART

Eike Hein hein at kde.org
Fri Apr 4 00:30:36 CEST 2008


------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=137074         
hein kde org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |NEW
      everconfirmed|0                           |1
            Summary|request for improvement -   |Don't close channel tabs on
                   |preference to not           |non-user-induced PART
                   |automatically close channel |
                   |tabs                        |



------- Additional Comments From hein kde org  2008-04-04 00:30 -------
I'm taking a renewed interest in this one. Renamed for clarity.

First of, the opening statement of the report is no longer true; losing connection to the server doesn't result in the views being closed. It's been that way for a while now. That creates an actual propblem, however, in that it makes the behavior inconsistent between connection loss and other reasons for a channel being PARTed by other means than a manual close, e.g. a kick. That's not good enough; it should either close every time, or stay open in both scenarios.

If we opt for the latter, the challenge becomes giving clear and hard-to-miss indication that a channel is not joined despite the view being open. 

We currently wipe a channel's nickname list on loss of connection, and the same should be done when keeping it open after a kick. Additionally, we need to make sure that an appropriate message always ends up being in that view, and at the end of the buffer. Furthermore, greying out the tab label might be nice to do, and showing a Rejoin action in the tab context menu.


More information about the Konversation-devel mailing list