GNOME Bugzilla – Bug 732054
Selection through mouse unreliable in route search popover
Last modified: 2014-08-11 00:40:49 UTC
Seems that a place somehow doesn't get selected and route is never searched for if you use mouse to select places from search results popover in the sidebar.
So the bug seems to be that when you hover a line it doesn't get "selected" or "mouse-overed" if you are above the sidebar. Try dragging the mouse down the list, if you are "above" the mapView it seems to work fine. But if you are "above" the sidebar it does not. Could someone confirm this? What could this mean?
No, it doesn't get selected when you 'click' on a line. It took some time to find out whats going on since it seems that result was selected and entry is populated with the selection but route doesn't get shown. Mattias found out ultimately that issue is that search result was never actually selected so the routing code doesn't have all the input it needs to start the route search.
This seems to work now with latest master of GTK+, could you guys test?
(In reply to comment #3) > This seems to work now with latest master of GTK+, could you guys test? Sure, as soon as I get gtk+ and gnome-maps built. I had to ditch my jhbuild install.
What still doesn't work properly is selection from the completion though.
(In reply to comment #5) > What still doesn't work properly is selection from the completion though. yeah, same here. Could you please mark this as duplicate of the gtk+ bug and open a new one for completion issue? It seems like a very different problems since it doesn't work with keynav either and the entry doesn't even get populated on selection.
(In reply to comment #6) > (In reply to comment #5) > > What still doesn't work properly is selection from the completion though. > > yeah, same here. Could you please mark this as duplicate of the gtk+ bug and > open a new one for completion issue? It seems like a very different problems > since it doesn't work with keynav either and the entry doesn't even get > populated on selection. ping?
*** This bug has been marked as a duplicate of bug 734129 ***