Summary: | [RFE] Allow the focus-under-mouse policy to be applied on the widget level | ||
---|---|---|---|
Product: | [Applications] konsole | Reporter: | davidblunkett <dav1dblunk3tt> |
Component: | general | Assignee: | Konsole Developer <konsole-devel> |
Status: | RESOLVED INTENTIONAL | ||
Severity: | wishlist | CC: | adaptee, kwin-bugs-null |
Priority: | NOR | ||
Version: | 0.9 | ||
Target Milestone: | --- | ||
Platform: | Unlisted Binaries | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: |
Description
davidblunkett
2010-12-03 18:37:12 UTC
What rule should be applied here? The current rule is that the _window_ below the mouse pointer gets focus. From what I understand, the _widget_ below the pointer should receive focus. If we change the rule, we have to be consistent and change it everywhere. I'm not sure I understand this comment. My point is that the window and the pane should follow the main KDE focus rule (in my case focus under mouse) but the panes in konsole do not follow this rule (obviously the window as a whole does follow this policy). The Panes in konsole require click to focus even though the kde policy is focus under mouse. To be clear I think that is the kde focus policy is "under mouse" then the konsole pane under the mouse should get focus. As it is you have to click the pane to set the focus when moving the mouse between panes. So currently in KDE, the focus policy is applied on the window level, not widget level, right? That explains the behavior quite well. Sorry - I see the confusion - yes the focus policy should apply at this level (widget level) I guess if this means the separate panes get focused under the mouse... I can confirm this bug for kde 4.6 I think this is a wish and can only be implemented by kwin. KWin cannot handle focus assignment inside toplevel windows. You'd have to read that setting from the kwin config so the only thing kwin could do here was to eg. set a property on the root window about the focus policy and/or emit a dbus signal clients could listen to. In case anyone wonders: tab focussing is handled by the widget style and anything but QEvent::MouseButtonPress will currently cause issues in at least some applications (notably konqueror) -> sending back to konsole Well, I think it is overkill to provide this convenience in a terminal emulator which is natually keyboard biased. And konsole already provides the "Next View Container" action for switching focus to next view container(default shortcut is Shift+Tab). So I will close it as WONTFIX. I disagree - you are simply refusing to honour the desktop focus policy. Surely there is a mouseover event that the pane can detect? |