Bug 239918

Summary:	Drag mode triggered on checkbox embedded into list view
Product:	[Plasma] Oxygen	Reporter:	Eike Hein <hein>
Component:	style	Assignee:	Hugo Pereira Da Costa <hugo.pereira.da.costa>
Status:	RESOLVED FIXED
Severity:	normal	CC:	hugo.pereira.da.costa
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	Linux
Latest Commit:		Version Fixed In:
Attachments:	System Tray Settings dialog

Description Eike Hein 2010-05-28 22:09:21 UTC

When pressing the left mouse button above a checkbox in the "Display" page of the the "System Tray Settings" dialog for too long, Oxygen goes into window drag mode. This is buggy behavior, because a checkbox works like a button in the sense that you're supposed to be able cancel the operation mid-way by dragging the cursor away before releasing the mouse button. This isn't possible if instead the window is dragged along.

Comment 1 Hugo Pereira Da Costa 2010-05-28 22:46:24 UTC

Screenshot of the "display" dialog you are referring too ? I can't seem to find it ...

Comment 2 Eike Hein 2010-05-28 22:53:43 UTC

Created attachment 47436 [details]
System Tray Settings dialog

It's available from the tray plasmoid context menu if you bring up the panel configurator. This is 4.5-beta1 btw.

Comment 3 Hugo Pereira Da Costa 2010-05-29 04:20:48 UTC

SVN commit 1131789 by hpereiradacosta:

Do not drag from KCategorizeView
BUG: 239918


 M  +3 -0      oxygenwindowmanager.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1131789

Comment 4 Eike Hein 2010-05-29 04:28:36 UTC

Confirmed fixed, thanks!

(But it uncovers a terrible, terrible bug in KCategorizedView: If you click above one checkbox and then drag away and release on another, it checks the checkbox you release on - it should make sure that press and release occured on the same item. So I have another one to bug now ...)

Comment 5 Eike Hein 2010-05-29 04:35:01 UTC

Bug 239940 in case you want to follow it.

Comment 6 Hugo Pereira Da Costa 2010-05-29 06:00:17 UTC

Yeah well. And in fact, the original bug (with drag) is also due to sloppy 
coding in kcategorizedView. oh well