maemo.org Bugzilla – Bug 4658
Documentation: HildonTouchSelectorEntry is unclear about auto-completion/text column
Last modified: 2010-03-15 20:53:28 UTC
You need to
before you can comment on or make changes to this bug.
The HildonTouchSelectorEntry description is rather unclear:
Some things I think it should mention more obviously, if they are true:
- There is no sense in having a HildonTouchSelectorEntry with multiple columns.
For instance, you couldn't use it to create a HildonTimeSelector class that
also allowed text to be entered as text.
So I don't know why it mentions "If you only need a text only, one column
selector ...". Maybe that's a copy/paste error.
Extra cell renderers in the single column could be useful, though only for
additional data (such as images) that would not be used in the auto-completion
or in the final text value.
- The (undocumented) text-property column is used to offer auto-completion
possibilities in the entry widget.
It should mention what kind of auto-completion matching is done. I guess
there is no way to get the entry widget, so there is no way to change from the
default case-sensitive matching.
For the record, you are filing bugs against the alpha release of hildon
(2.1.42). There is a beta already (2.1.62) and the current version in git is at
We would appreciate if you review your comments against something that's not so
(In reply to comment #1)
> For the record, you are filing bugs against the alpha release of hildon
> (2.1.42). There is a beta already (2.1.62) and the current version in git is at
I mistyped the one URL in this one bug. There's no need to exaggerate.
I do see that there is now a function to get the entry, mentioned in the
description: "For more specific use cases, the HildonEntry can be accessed
directly with hildon_touch_selector_get_entry()". That's great, but the default
behavior should still be described, and the documentation should suggest why
you might want to use that entry, for instance to change the autocompletion
My other comments also still seem to apply.
(In reply to comment #0)
> - The (undocumented) text-property column is used to offer auto-completion
> possibilities in the entry widget.
I have just reviewed it. The property was documented, but it seems that gtk-doc
output for the deprecated elements is different, depending on his type. On the
functions it adds a "Warning: deprecated blabla", but on the properties the
text after "Deprecated:" is ignored. My error was put all the description of
this property after the "Deprecated:"
I have fixed it right now, on the git repository, explain the global use of the
property, and explain that it is deprecated, and that
HildonTouchSelectorColumn:text-property should be used instead. I maintain the
"Deprecated:" in order to allow this property to be included on the list of
(Anyway this is not the real reason of the bug)
Thanks for your help
Author: Xabier Rodriguez Calvar <firstname.lastname@example.org>
Date: Fri Jan 29 16:38:00 2010 +0100
Improved docs of HildonTouchSelectorEntry about columns management.
Fixes: NB#4658 (Documentation: HildonTouchSelectorEntry is unclear
about auto-completion/text column)
Setting explicit PR1.2 milestone (so it's clearer in which public release the
fix will be available to users).
Sorry for the bugmail noise (you can filter on this message).