Bug 65531 - desktop keep mouse focus when menu translucency is enabled
Summary: desktop keep mouse focus when menu translucency is enabled
Status: RESOLVED DUPLICATE of bug 64944
Alias: None
Product: kdelibs
Classification: Unmaintained
Component: kstyle (other bugs)
Version First Reported In: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Karol Szwed
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-05 12:58 UTC by g.persia
Modified: 2004-03-05 03:16 UTC (History)
0 users

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description g.persia 2003-10-05 12:58:53 UTC
Version:            (using KDE KDE 3.1.4)
Installed from:    Debian testing/unstable Packages
Compiler:          gcc version 3.3.2 
OS:          Linux

When the menu translucency is enabled and you click in the konsole window SOMETIMES (erratic behaviour) the desktop keep the focus: if you start typing something, one of the desktop link gets activated (the last selected item or one whose name start with the key pressed).
My focus-policy is "click to get focus".

I've noticed that if I disable the menu translucency this doesn't happen.

I don't know how to reproduce this error because it happens only (but not always) when translucency is enabled.

Oh, the konsole get the focus too! what I type is showed in the command line.
Comment 1 g.persia 2003-10-05 18:09:01 UTC
I was trying to reproduce the bug and I've noticed that kstyle settings don't 
matters. 
The problem arises when you click THE TITLE BAR of ANY window: even if it gets 
the focus, the desktop "keeps listening" at the keyboard. If you press enter 
the item selected runs...  if you press any key, say "c", the first item 
starting with "c" gets selected. 
 
Only the first virtual desktop has this problem: I've tried to reproduce the 
bug in the second (and third, etc.) virtual desktop[s]: they works well. (!?) 
 
I apologise for the mistake. 
Should I open a new bug and mark this as resolved? 
 
 
Comment 2 Maksim Orlovich 2003-10-05 18:20:38 UTC
Does this sound like #64944 to you too?  
 
Comment 3 g.persia 2003-10-05 19:13:36 UTC
I've tried with google and MLs. 
It seems nobody knew this bug out there. 
 
I had no luck with SimpleSearch for bugs. 
Thanks for pointing. 
 
For curiosity's sake: why this happens only in the first virtual desktop? 
 
Comment 4 Maksim Orlovich 2004-03-05 03:16:54 UTC
No idea, sorry

*** This bug has been marked as a duplicate of 64944 ***