[hafqa] [hafqa] [Bug 780] GTK "row-activated" signal has faulty "double click" detection
From: bugzilla-daemon at maemo.org bugzilla-daemon at maemo.orgDate: Wed Sep 27 11:21:36 EEST 2006
- Previous message: [hafqa] [Bug 779] gtk_arrow_new broken
- Next message: [hafqa] [Bug 779] gtk_arrow_new broken
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
https://maemo.org/bugzilla/show_bug.cgi?id=780 tommi.komulainen at nokia.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From tommi.komulainen at nokia.com 2006-09-27 11:21 ------- This is how it is supposed to work. Double-clicking (on a touchscreen) is not very convenient interaction, which is why we have this 'activate when tapping on an already focused item' instead. Yes, it may need unlearning some old habits, but we believe this is better for a touchscreen device. This is unlikely to change. I'll agree that in the case the treeview does not already have focus and you tap on the row where the cursor will be, it probably shouldn't activate that row just yet. Unfortunately, as I recall, this was difficult to prevent, but OTOH it is not an often occuring use case. Would you mind filing a new bug which addresses only this latter part? It would help us avoid mixing unfixable parts with fixable bugs. -- Configure bugmail: https://maemo.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.
- Previous message: [hafqa] [Bug 779] gtk_arrow_new broken
- Next message: [hafqa] [Bug 779] gtk_arrow_new broken
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]