[Konversation-devel] [Bug 132891] New: server list allows identical network names, creating conflicts in the watched nickname list

[Niek Beernink]

------- 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=132891         
           Summary: server list allows identical network names, creating
                    conflicts in the watched nickname list
           Product: konversation
           Version: unspecified
          Platform: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: konversation-devel kde org
        ReportedBy: omega blackcatgames com


Version:           0.19+ #3131 (using KDE 3.5.4, Kubuntu Package 4:3.5.4-0ubuntu6 )
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.15-25-k7

Currently the server list allows for identically named networks. This becomes a problem when you want to add a nickname to a certain server, but since the labels are the same, you don't quite know which one is which. 

Now, I'm not quite sure how to best describe this...

The problems that I see when a user has two identical server names are;

1. The network selection box in watched nicks (Settings => Configure Konversation... => Watched nicks) that lets you adjust the network on which you're watching a nick stops working correctly. It doesn't re-assign the nick to the network you selected since it has the same name.

2. When you're connected to the second identically named network, and you've added a nickname to watch on the first identically named network then rightclicking on a nickname and selecting "Add to watched nicks" is not possible.

3. Similar to point 2. If you're connected to the second network, and you aren't watching a nick on the first server, then right-clicking on a nick and selecting "Add to watched nicks" will add the nick to the first server in the list.

To fix this, users should be disallowed to use an identical server name.

I can provide steps to reproduce if needed. Just ask.