Bug 254994 - klipper doesn't pup-up at mouse position
Summary: klipper doesn't pup-up at mouse position
Status: RESOLVED FIXED
Alias: None
Product: klipper
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Mandriva RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: Esben Mose Hansen
URL:
Keywords:
: 244620 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-10-22 21:27 UTC by Richard Neill
Modified: 2011-12-28 22:42 UTC (History)
6 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 Richard Neill 2010-10-22 21:27:06 UTC
Version:           unspecified (using KDE 4.5.0) 
OS:                Linux

If I press Ctrl-Alt-V, the klipper window should appear right where I want it, under the mouse-pointer. This used to be the PopupAtMousePosition option. However, this doesn't work any more (and the option is no longer present in the Klipper configuration).

This is particularly irritating on a large screen: the klipper window is 3200 pixels away from where I expect to find it!

Reproducible: Always
Comment 1 Hans-Rudi Denzler 2010-10-23 12:44:57 UTC
In "system tray settings > 2. group" you can add a shortcut, but klipper doesn't popup at mouse position as the action menu does.

Having both options could be a wish, right ?

- mark (*) in firefox "https://bugs.kde.org/show_bug.cgi" > klipper > call actions manually --> action menu doesn't pop up at mouse position (*)
- mark (*) in kwrite "https://bugs.kde.org/show_bug.cgi" --> action menu does pop up already at mouse position (*).
Comment 2 Richard Neill 2010-10-23 17:52:35 UTC
This is definitely a regression since 4.3.

 - In KDE 3.5, there was an option checkbox for whether to popup at mouse position or not (and it worked either way).
  
 - In KDE 4.3, the option checkbox had been removed, but the default behaviour is correct (pop up next to mouse)

 - In KDE 4.5 it's now broken. 

Sorry I can't give a more specific marker for the regression point.
Comment 3 Richard Neill 2010-11-02 02:41:13 UTC
Still broken in 4.5.2
Comment 4 megabaks 2010-11-07 22:56:41 UTC
*** This bug has been confirmed by popular vote. ***
Comment 5 j.p.cleverdon 2011-03-13 21:20:36 UTC
Still broken in 4.6.1, as installed on Ubuntu 10.10 from ppa:kubuntu-ppa/backports

I changed the keyboard shortcut key from the default and that didn't help.  The pop-up window still refuses to pop up, either with the default setting, Ctrl-Alt-V, or a custom one, Ctrl-Alt-B.

(By the way, I agree with bug # 259539, moving the klipper pop-up shortcut key setting from the klipper config into System Settings -> Shortcuts and Gestures -> Global Keyboard Shortcuts -> Klipper is obscure to the point of uselessness.)
Comment 6 Richard Neill 2011-07-03 18:17:30 UTC
Still broken in 4.6.3, I'm afraid.

At least there is a workaround: run the program "parcellite", which is an almost exact replacement, and works perfectly.
Comment 7 Martin Klapetek 2011-12-02 18:18:12 UTC
Git commit 90944a8c6bb9e22e4089870f49f898eec083518d by Martin Klapetek.
Committed on 02/12/2011 at 19:11.
Pushed by mklapetek into branch 'master'.

Fix regression in Klipper, which broke the "Show at mouse position" feature back in 4.5.

Committing this with i18n approval.

REVIEW: 103196
BUG: 254994
CCMAIL: lueck@hube-lueck.de

M  +7    -1    klipper/klipper.cpp
M  +1    -0    klipper/klipper.h

http://commits.kde.org/kde-workspace/90944a8c6bb9e22e4089870f49f898eec083518d
Comment 8 Kevin Kofler 2011-12-25 14:51:50 UTC
*** Bug 244620 has been marked as a duplicate of this bug. ***
Comment 9 Silver Salonen 2011-12-28 21:38:14 UTC
One issue though, a custom shortcut (ctrl+alt+v) seems not to stick over sessions.
Comment 10 Jekyll Wu 2011-12-28 22:42:46 UTC
(In reply to comment #9)
> One issue though, a custom shortcut (ctrl+alt+v) seems not to stick over
> sessions.

If you are talking about this re-added global shortcut instead of the global shortcut provided by systray, I think that issue has been fixed recently. So wait for next RC to check it again.