[hafqa] [hafqa] [Bug 780] New: GTK "row-activated" signal has faulty "double click" detection
From: bugzilla-daemon at maemo.org bugzilla-daemon at maemo.orgDate: Tue Sep 26 22:43:48 EEST 2006
- Previous message: [hafqa] [Bug 779] New: gtk_arrow_new broken
- Next message: [hafqa] [Bug 780] GTK "row-activated" signal has faulty "double click" detection
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
https://maemo.org/bugzilla/show_bug.cgi?id=780 Summary: GTK "row-activated" signal has faulty "double click" detection Product: haf Version: unspecified Platform: All OS/Version: Linux Status: NEW Severity: minor Priority: P2 Component: hildon-libs AssignedTo: luc.pionchon at nokia.com ReportedBy: mike at w4g.org QAContact: hafqa at maemo.org The "row-activated" signal is supposed to be emitted by a GtkTreeView element when a row is double clicked. The Hildonized GTK emits the signal if the row is selected already selected and then it is clicked. When the GtkTreeView is first shown the the first row will be selected by default but not highlighted. If the user clicks it to highlight it then the "row-activated" signal is incorrectly emitted. Or if he selects a row, and then minutes later clicks it again then the "row-activated" signal is emitted. It can be worked around by checking the interval between the "cursor-changed" signal (actually two signals ago since the click that emits the "row-activated" will also emit a "cursor-changed") and the "row-activated" signal. -- 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] New: gtk_arrow_new broken
- Next message: [hafqa] [Bug 780] GTK "row-activated" signal has faulty "double click" detection
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]