maemo.org Bugzilla – Full Text Bug Listing
|Summary:||HildonTouchSelector: Can't jump to entries with keyboard (type ahead)|
|Product:||[Maemo Official Platform] Desktop platform||Reporter:||Murray Cumming <murrayc>|
|Component:||hildon-widgets||Assignee:||Claudio Saavedra <csaavedra>|
|Status:||RESOLVED DUPLICATE||QA Contact:||hildon-libs-bugs|
|Priority:||Low||CC:||andre_klapper, marius, quim.gil, urho.konttori|
It's tedious to scroll down long lists in HildonTouchSelector, such as a list of countries, even with the kinetic scrolling. People expect it to jump to an entry when they press a key on the keyboard, as they could in a web page's combo box. Note that GtkComboBox (HildonTouchSelector's equivalent in the regular GTK+ API) doesn't support this yet either https://bugzilla.gnome.org/show_bug.cgi?id=567141 though GtkComboBoxEntry and HildonTouchSelectorEntry do via GtkEntryCompletion. However, I've noticed that the Maemo 5 address book seems to support this feature somehow.
For testing this, enable the extras-devel repository in the application manager, select 'all categories' (since you will *never* guess the right one anyway, in my experience) and try to find a package with a name starting with something like 'p'.
It would be indeed good to know what is the problem and how trivial/complex would be to implement a solution. It's a functionality really appreciated when found in Maemo 5. The 'bug' here would be that from a user point of view jumping after typing is expected funtionality, working in some applications and parts of the system but not in others, which is confusing and affects the overall experience.
We are working on this. The solution is not exactly the proposed one, but close enough. Will be available in the first update release. Implementation is done, but not totally verified.
(In reply to comment #3) > We are working on this. The solution is not exactly the proposed one, but close > enough. Will be available in the first update release. Implementation is done, > but not totally verified. > Care to elaborate on what the solution is? It's nice to know that it's being worked on, but it's even better to have an idea about what exactly /it/ is.