Open GoogleCodeExporter opened 9 years ago
jeff is working on this.
Original comment by yanokwa
on 6 Aug 2011 at 4:24
We'll have to rework this somehow. The problem is that the autocomplete is
currently implemented as a select1, which works for filling out a form.
However, when you load a saved form javarosa checks to see that the saved value
matches a value in the select one, and when it doesn't match it silently throws
it away, which seems like bad behavior. We could implement it as a "string"
instead of a select1, but then we have to figure out where to store the list
and how to reference where the list is stored.
Original comment by carlhart...@gmail.com
on 29 Sep 2011 at 10:44
Issue 307 has been merged into this issue.
Original comment by yanokwa
on 21 Oct 2011 at 7:53
filed javarosa bug at
https://bitbucket.org/javarosa/javarosa/issue/52/add-support-for-open-select-one
-in-prompts
Original comment by yanokwa
on 21 Oct 2011 at 7:53
Assuming that the patch attached to issue 307 is applied Collect appears to
implement the "closed" behaviour safely enough that it can be reintroduced.
This patch does just that.
Original comment by matt.ad...@radicaldynamic.com
on 24 Nov 2011 at 6:50
Attachments:
we chatted about this and decided the old implementation also wasn't adequate.
Popping up a toast and clearing the answer is likely to be missed and lead to
lost data, and is inconsistent with the rest of Collect. The "closed" behavior
should act more like a constraint and prevent the user from moving on if a bad
value is entered. That functionality, I think, will have to be added in the
javarosa core. Until then we're going to continue to leave out autocomplete.
Original comment by carlhart...@gmail.com
on 29 Nov 2011 at 3:27
Original comment by yanokwa
on 25 May 2012 at 8:11
any updates on this bug. Would be nice to have the autocomplete feature
working.
Original comment by ngam...@gmail.com
on 4 Feb 2015 at 8:28
Original issue reported on code.google.com by
carlhart...@gmail.com
on 4 Aug 2011 at 8:56