autocomplete replaces label with value

[GoogleCodeExporter]

Let's say i have a list like this (key/value pairs or in ODK
terminology value/label pairs)

value='12345', label='first item'
value='12346', label='second item'

Now. let's say I am entering items and I start keying in 'first' which
offers me only one option (first item) that I select. Then, I move to
the next screen and move right back (let's say i want to modify
something). In the original screen where I entered the first item I
now see '12345' and not 'first item' as the app initially inserted
when selecting the filtered item. The final problem actually happens
after swiping forward from this screen since the app tells me
"Warning: 12345 does not match any answers. No answer recorded." and
clears the input box.

It seems that the autocomplete widget replaces the label with the
value but it does not actually allow filtering by value which means
that if the user goes back to view the result and forward again, he or
she loses the input.

Original issue reported on code.google.com by yanokwa on 22 Aug 2011 at 2:27

[GoogleCodeExporter]

Original comment by yanokwa on 21 Oct 2011 at 7:53

• Changed state: Duplicate
• Added labels: Collect

[GoogleCodeExporter]

This is not actually a duplicate issue and can be fixed with a simple one-line 
change.  See attached patch against e45b5ae652fb.

Original comment by matt.ad...@radicaldynamic.com on 24 Nov 2011 at 2:40

Attachments:

• e45b5ae652fb.patch

[GoogleCodeExporter]

Hi Matt, I remember noticing them backing out the autocomplete functionality 
within the latest release of odk collect. Is that correct or which 
version/tag/changeset does your fix apply to?

Original comment by spuzv...@gmail.com on 24 Nov 2011 at 2:46

[GoogleCodeExporter]

As mentioned in my comment, the fix applies to e45b5ae652fb as mentioned.  This 
does not re-enable autocomplete functionality but fixes the specific problem 
that was reported in this issue before it was marked as a duplicate (which it 
isn't from what I can tell).

Any patches to re-enable autocomplete functionality will go against issue 289.

Original comment by matt.ad...@radicaldynamic.com on 24 Nov 2011 at 6:40

[GoogleCodeExporter]

Original comment by carlhart...@gmail.com on 29 Nov 2011 at 3:22

• Changed state: New

[GoogleCodeExporter]

This issue was closed by revision 61302d0a2061.

Original comment by carlhart...@gmail.com on 29 Nov 2011 at 3:38

• Changed state: Fixed

[GoogleCodeExporter]

This issue was closed by revision ac7749ddaa79.

Original comment by carlhart...@gmail.com on 29 Nov 2011 at 5:08