Bug 132103

Summary: DCC status window button access keys conflict with channel access keys
Product: [Applications] konversation Reporter: Niek Beernink <n.beernink>
Component: generalAssignee: Konversation Developers <konversation-devel>
Status: RESOLVED FIXED    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:

Description Niek Beernink 2006-08-09 02:33:35 UTC 
Version:           0.19+ #3119 (using KDE KDE 3.5.4)
Compiler:          gcc (GCC) 4.1.2 20060715 (prerelease) (Ubuntu 4.1.1-9ubuntu1)  
OS:                Linux

Pressing the acces keys for the buttons in the DCC status window sometimes conflict with the acces keys for the channels.
This probably differs from user to user since everybody visits different channels. But for me, pressing alt+d for the "DCC Detail" button brought me to #kubuntu-devel since the "d" was the access key for that channel. 

This probably happens for the other buttons in the DCC Status window as well.
Comment 1 Niek Beernink 2006-08-18 00:01:06 UTC 
These buttons now work when the "tabs" are placed left.
Comment 2 Peter Simonsson 2006-08-24 16:38:24 UTC 
Fixed in svn trunk by letting the accel manager do the assigning of accels
Comment 3 Niek Beernink 2006-08-24 16:54:29 UTC 
I sent you the patch for this. But the behavior can still be reproduced by doing the following;

1. Send a file to someone and select it in the DCC status window so the buttons in that window are enabled.
2. If the open button has an acceleration key o, then join #o
3. Notice how this new channel now gets an acceleration key o.
4. Switch back to the DCC status window.
5. Press alt+o for Open File and notice how it switches to #o instead.

I know that single letter channels are quite uncommon and that because of this, the scenario isn't likely to happen. In any case, it's much better now that the acceleration keys on those buttons are no longer static. 

Just wanted to let you know. :)
Comment 4 Peter Simonsson 2006-08-24 16:57:44 UTC 
well that's a bug in the accel manager and there's nothing I can do about it