Bug 138077 - usability: systray icon and RMB -- show menu at the icon not at the mouse cursor location
Summary: usability: systray icon and RMB -- show menu at the icon not at the mouse cur...
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kicker
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR wishlist
Target Milestone: ---
Assignee: Aaron J. Seigo
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-11-29 12:51 UTC by Maciej Pilichowski
Modified: 2009-09-08 00:01 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 Maciej Pilichowski 2006-11-29 12:51:32 UTC
Version:            (using KDE KDE 3.5.5)
Installed from:    SuSE RPMs

It is a bit of annoyance -- since the menu is shown at mouse cursor location if I clicked by mistake I cannot see clearly the rest of the systray icons and I have to click in a more limited area. 
 
 Please compare it to clear displaying menu like KMenu, "last visited" toolbar button in Kate, or simply any menu -- they are displayed next to the item, not next to the cursor mouse. 
 
 In context of systray, the displayed menu should be treated as a menu, not a classic popup, since such icon is no an app (compare it to maximized Konqueror for example and its popup menu).
Comment 1 Stefan Winter 2006-11-29 17:46:52 UTC
Reassigning to kicker, since this is a default behaviour for every systray icon, not a KWiFiManager issue. See RMB click on KAlarm, KTorrent, KMail or whatever systray icon you like.
Comment 2 Maciej Pilichowski 2006-11-29 19:26:21 UTC
Stefan, not true -- compare Klipper (turn off popup menu positioning at mouse cursor).

(I am not able to reassign)
Comment 3 Stefan Winter 2006-11-29 19:46:32 UTC
Ah, I see - but I think it still belongs to kicker. What you propose makes sense to me (to be honest, I was annoyed by it as well some rare times, but didn't care enough to do something about it). But the way it is now, every single applet would need to implement a config option to not use the default behaviour - quite a bloaty nightmare. Changing the behaviour by default would make much more sense IMHO.

I reassigned the bug to kicker, and so it ended up at Aaron Seigo, maybe he has some thoughts on this?
Comment 4 A. Spehr 2009-05-23 04:41:56 UTC
Kicker is currently unmaintained, you can look to your distribution for help, however.
Comment 5 Maciej Pilichowski 2009-05-23 09:10:49 UTC
The _issue_ is still valid, the fact we now have the plasma instead of kicker does not change a thing. Please change the product only (there is no point in sending the _same_ report again).

Thank you.
Comment 6 FiNeX 2009-09-08 00:01:48 UTC
Kicker is no more mantained and all bugs/wishes will not be fixed/implemented in KDE3. A list of the most interesting/unresolved issues which is still valid for KDE4 has been created. Before reopening old kicker bugs on KDE4 Plasma, please try the new KDE 4.3.1, check the current behaviour and, only if you find new bugs or if you need a particular feature, open a new bug report.

Remember that KDE 4 is a full rewrite of KDE 3 so some old features will not be re-implemented because the behaviour has be changed a lot on some sides.

Thanks for the comprehension and enjoy the new KDE 4!

-- 
FiNeX & D. Andres