| Summary: | JJ: Configurable actions in "PresentWindows"-Effect | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | patrick.schwalm |
| Component: | compositing | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | wishlist | CC: | anarchic.teapot, flabbergasted, m, marcomelo, pgalves, phlogi1 |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Bug is no longer resolved, please fix again. | ||
|
Description
patrick.schwalm
2008-06-03 08:55:49 UTC
FWIW I'd like to have some kind of configuration for what the buttons do (on my TODO list is to actually add this myself... but I'll have to see how much time I have, and how much it bothers me :). I personally want a "Move to Current Desktop" action associated with it, as I find that the most often used; but every user will have his own workflow, so I think we should make it configurable. You can move between desktops in DesktopGrid using two right-clicks rather easily. > You can move between desktops in DesktopGrid using two right-clicks rather easily.
This behavior is completely hidden. I (=regular, but evidently noob-ish user of KDE4) didn't know this until I saw this bug.
I notice that middle click does the same thing (makes window appear on all desktop). So, a way to resolve this bug is to allow some configuration of what each mouse button would do in the Desktop Grid view, as Kelvie Wong suggests. This would also make the current behavior more obvious to the user.
*** Bug 184538 has been marked as a duplicate of this bug. *** I second karthik, Although is is handy to have this function I don't like the specifics of this idea because the function is hidden to all but the savvy user. A better approach is to provide a set of buttons for different functions that might appear when hovering over a window in the "present" view (OSX does this I believe). If an individual wants to be able to bind a particular opertion like close to a "free" mouse button then this should be possible - it should just not be _the way_ the feature is delivered. *** Bug 185035 has been marked as a duplicate of this bug. *** *** Bug 188035 has been marked as a duplicate of this bug. *** Any news on this? This is still one of the main reasons I still don't use KDE4 and it seems like a really small feature to implement. And it would make all the users switching from Compiz happy. *** Bug 195401 has been marked as a duplicate of this bug. *** *** Bug 195401 has been marked as a duplicate of this bug. *** *** Bug 197955 has been marked as a duplicate of this bug. *** SVN commit 988788 by graesslin: Configurable mouse actions in present windows for clicking a window and desktop. It's possible to activate a window, exit without activating, bring window to current desktop, send window on all desktops, mimize the window and close the window. Clicking desktop allows to activate selected window, exit without activating, show the desktop (minimize all apps) and of course do nothing. FEATURE: 163116 M +30 -0 effects.cpp M +5 -0 effects.h M +110 -4 effects/presentwindows/presentwindows.cpp M +29 -0 effects/presentwindows/presentwindows.h M +40 -0 effects/presentwindows/presentwindows_config.cpp M +346 -93 effects/presentwindows/presentwindows_config.ui M +6 -1 lib/kwineffects.h WebSVN link: http://websvn.kde.org/?view=rev&revision=988788 Created attachment 93742 [details]
Bug is no longer resolved, please fix again.
Please bring this feature back. I don't know why but it appears that this featured was implemented but was removed at some point. The attached screenshot shows that the feature from 4.3 no longer exists in the latest version of KDE4 and likely doesn't exist in KWin 5 either.
Please reimplement this or at the very least allow Middle Click Close + Modifier in the Window Actions. I would be ok with either option.
The actions *are* configurable, close was removed deliberately => bug #321190 |