Carl:
I'm looking at a comment that you made on 6ed2c263f4c1 "removing
autocomplete from 1.1.7 release until we can fix it", wondering what the
actual problem is and whether it is related to issue #289/JavaRosa #52
or if there is something else going on here.
I'd like to get this fixed. Please let me know if there is something
specific that I should know.
Thanks,
Matt
https://code.google.com/p/opendatakit/issues/detail?id=289&q=autocomplete
matt,
it's because of jr bug #52 that we are removing autocomplete. it's
going to take a bit of code to add the open/closed selection in the
javarosa-core and the cycles aren't there. feel free to take a crack
at it (or to convince dimagi to do the same :)).
we do have an alternative approach (loading values from a csv) that we
are considering. that approach would also solve some memory issues
we've seen with dynamic itemsets. glad to flush this out a bit more if
someone is interested in moving us closer to implementation.
yaw
Matt,
The issue is JavaRosa #52.
Currently if you have a select1, it will allow you to save a value not part
of the list. However, if you load an instance (or include a default value)
not part of the list, that value is silently discarded. We don't want
users losing data so we decided to not include the feature.
The fix needs to be in the javarosa core, but in talking to the Dimagi guys
it sounded non-trivial. We don't have the cycles to tackle this right now,
but if you want to give it a go that'd be awesome.
-Carl
Carl:
I'm looking at a comment that you made on 6ed2c263f4c1 "removing
autocomplete from 1.1.7 release until we can fix it", wondering what the
actual problem is and whether it is related to issue #289/JavaRosa #52 or
if there is something else going on here.I'd like to get this fixed. Please let me know if there is something
specific that I should know.Thanks,
Matt
https://code.google.com/p/**opendatakit/issues/detail?id=**
289&q=autocompletehttps://code.google.com/p/opendatakit/issues/detail?id=289&q=autocompletehttps://bitbucket.org/**javarosa/javarosa/issue/52/**
add-support-for-open-select-**one-in-promptshttps://bitbucket.org/javarosa/javarosa/issue/52/add-support-for-open-select-one-in-prompts--
Matt Adams
Radical Dynamic
www.radicaldynamic.com
Carl & Yaw:
Thanks for the additional clarification.
From what I can tell "closed" autocomplete is correctly implemented in
Collect as of e45b5ae652fb as long as the patch that I attached to issue
#307 is also applied. A warning toast ensures that user input is not
silently ignored.
I think it is safe to reintroduce this closed-behaviour autocomplete
functionality as-is.
I took a cursory glance at the JavaRosa code and I think that I can
implement both open/closed without too much trouble. I will probably
have a patch for this soon.
Cheers,
Matt
carl and i apparently share a brain.
It is a fine brain to share.
You mention: "we do have an alternative approach (loading values from a
csv) that we
are considering. that approach would also solve some memory issues
we've seen with dynamic itemsets."
What do you think of using the CSV approach as a way of loading previous
answers from respondants who are interviewed on multiple occasions?
I am thinking along the lines of
How much money do you earn per month?
(previous answer from July 2011 = $80)
Where the respondent would be identified and his/her previous answers could
be drawn from the CSV of previous surveys, then displayed to the enumerator
for purpose of comparison.
☞§※☼:airplane:
~Neil
carl and i apparently share a brain.