Bug 226628 - setup window shortcut should immediately give focus to setup new keybinding
Summary: setup window shortcut should immediately give focus to setup new keybinding
Status: RESOLVED DUPLICATE of bug 182873
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-13 04:54 UTC by Jake Martin
Modified: 2010-10-06 21:42 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jake Martin 2010-02-13 04:54:36 UTC
Version:            (using KDE 4.4.0)
Compiler:          gcc (Gentoo 4.3.4 p1.0, pie-10.1.5) 4.3.4  
OS:                Linux
Installed from:    Compiled From Sources

In KDE 3.5.10 and previous, I set up a very handy window shortcut (CTRL-ALT-W) for setting up a window shortcut in the active window. 

Thus, if I was in a window, I could press CTRL-ALT-W and the setup window shortcut menu would come up *with the focus ready* for me to immediately enter the new shortcut key sequence for that window.

However, in KDE 4.4.0, when I press CTRL-ALT-W, the setup window shortcut menu comes up *without the focus ready* so that I have to mouse click in the setup window shortcut dialog before I can enter the new shortcut key sequence.

I hope can be alleviated easily.
Comment 1 Christoph Lange 2010-09-15 11:20:45 UTC
I think this is a duplicate of bug 211791.
Comment 2 Thomas Lübking 2010-09-15 13:38:05 UTC
depends:
if it's like 
a) "the shortcut button should have the focus" - yes.
but it rather sounds like
b) "the shortcut window should be activated" - though latter one happens here with every focus policy/protection i've tested (many ;-)

@Jake
is this b) and still a present issue and what focus policy / protection level combination do you use?
Comment 3 Thomas Lübking 2010-09-15 13:42:32 UTC
oh.. and in case of a) it would be a dupe of bug #182873 which is obviously NOT a dupe of #211791
Comment 4 Jake Martin 2010-10-06 01:24:46 UTC
Hey guys, sorry it took me so long to get back to you!

I don't think my bug is a duplicate of bug 211791 because my bug has to do with the "setup window shortcut" dialog and not the "global shortcuts" window accessible from krunner as in bug 211791.  So, I created a shortcut for "setup window shortcut," but since the change to 4.X from 3.5X, this has become very cumbersome to do with only the keyboard.

@Thomas
The focus policy idea was a very good one. However, I just tried with "focus stealing prevention level" set to "None" and the "Policy" set to "Click to Focus" and it still doesn't set the focus to the shortcut key as it should.

Essentially, I just wanted to be able to use the "setup window shortcut", and then immediately enter the new shortcut for the active window, press enter, and be on my way.
Comment 5 Thomas Lübking 2010-10-06 18:57:04 UTC
so the client (the window) has the focus, but not the proper element (shortcut button) - that's true and makes this a dupe of #182873, where there is attached a fixing patch =)

(if by any chance i got you wrong and this is not the same bug and issue and fixed by the patch, please resetn the dupe status)

*** This bug has been marked as a duplicate of bug 182873 ***
Comment 6 Jake Martin 2010-10-06 21:42:44 UTC
That's right Thomas!  It was a dupe of bug 182873.  

Thanks so much for the patch and also your attention.  It was a pleasure, sorry for the dupe.