Bug 128107

Summary:	double clicking too fast within the interval does nothing
Product:	[Plasma] kwin	Reporter:	Erin Clark <hippiegurlerin>
Component:	decorations	Assignee:	KWin default assignee <kwin-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	jonas.vejlin, sniffy
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Slackware
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Erin Clark 2006-05-27 03:02:08 UTC

Version:            (using KDE KDE 3.5.2)
Installed from:    Slackware Packages
OS:                Linux

whenever I doubleclick on the icon on the menubar sometimes if i click too fast it will not do anything even though it is within the doubleclick interval, this applies to all themes that use the doubleclick to close feature.  It seems really inconvienient to do it this way because you have to time the doubleclick just right, cant it be fixed to where it accepts quicker doubleclicks?

Comment 1 David Faure 2006-05-29 15:10:14 UTC

There are no icons in menubars; is this about the panel (which is by default at the bottom of the screen)?

Comment 2 Erin Clark 2006-05-29 17:11:47 UTC

er sorry not menubar, i meant the icon on the titlebar

Comment 3 David Faure 2006-05-29 17:22:20 UTC

Ah this is about the icon that pops up the window-manager menu with advanced / to desktop / move / resize etc.?
OK, kwin issue then.

Comment 4 Chris Gow 2006-09-09 22:02:51 UTC

I can not reproduce this problem in Kubuntu 6.0.6/KDE 3.5.4. Erin, does this still happen to you?

Comment 5 Erin Clark 2006-09-10 22:15:28 UTC

I just tried it on Slackware 10.2/KDE 3.5.4 and it does still happen to me

Comment 6 Jonas Vejlin 2009-04-04 15:55:47 UTC

Do you stil have this problem with recent version of kwin?

Comment 7 Martin Flöser 2009-12-19 14:30:49 UTC

(In reply to comment #6)
> Do you stil have this problem with recent version of kwin?
Does not seem like it is still a problem, but there is the three click bug and I set it as duplicate

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