Bug 154697 - clickevents go to wrong instance and therefore menu launcher appearing at wrong position
Summary: clickevents go to wrong instance and therefore menu launcher appearing at wro...
Status: RESOLVED NOT A BUG
Alias: None
Product: plasma4
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
: 156906 158864 (view as bug list)
Depends on:
Blocks:
 
Reported: 2007-12-27 20:01 UTC by Edwin Schepers
Modified: 2008-06-16 04:45 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Edwin Schepers 2007-12-27 20:01:44 UTC 
Version:           svn (using KDE 3.97.1 (KDE 4.0 >= 20071214), compiled sources)
Compiler:          gcc
OS:                Linux (x86_64) release 2.6.22-5-default

Hi,
When I hit the K-button the menu appears. When I then select one of the apps in the taskbar, the menu disappears, but the app doesn't react. Instead, the menu appears and disappears after repeatedly clicking the app.
Comment 1 Jason Stubbs 2007-12-29 08:24:17 UTC 
This is another qt bug related to qgraphicsitem mouse grabbing. If you move the mouse by even a pixel after the first click, the next click will do what it's supposed to do.
Comment 2 Sebastian Sauer 2008-02-20 01:06:54 UTC 
*** Bug 156906 has been marked as a duplicate of this bug. ***
Comment 3 Sebastian Sauer 2008-02-20 01:29:06 UTC 
better summary, this can be btw still reproduced with 4.4 with current trunk.
Comment 4 Sebastian Sauer 2008-03-06 22:33:54 UTC 
*** Bug 158864 has been marked as a duplicate of this bug. ***
Comment 5 Sebastian Sauer 2008-03-06 22:35:35 UTC 
better summary ;)
Comment 6 Aaron J. Seigo 2008-06-16 04:45:03 UTC 
this is problem in the design of event in qgraphicsview. trolltech is aware of it, there's nothing we in plasma can do about it, hopefully it gets fixed in some fashion some day. but it certainly an upstream bug.