I am seeing this behavior where the radio button highlight disappears after
you make your selection.
My experience is that the radio dot disappears, but the data is still
recorded, dependent skip logic seems to still work.
It's not good feedback for the user, though, and it will be confusing for
the enumerators in the field. Is there any thoughts on why this is
happening?
A short video is attached for fun viewing!
thanks,
Neil
Just to confirm -- that is with the rev 126 release (the one downloadable
from the site)?
We haven't seen that in our testing but have seen other focus-highlight
issues.
Are you using the async database prompts on this page that I pointed you to?
Can you share your form?
The next release will be switching to use bootstrap, so this problem will
likely no longer exist, but it might morph in interesting ways. (One reason
for the switch is to address a different issue with interactions between
text boxes and selection lists).
ยทยทยท
On Mon, Mar 30, 2015 at 5:41 PM, Neil Hendrick wrote:
I am seeing this behavior where the radio button highlight disappears
after you make your selection.
My experience is that the radio dot disappears, but the data is still
recorded, dependent skip logic seems to still work.
It's not good feedback for the user, though, and it will be confusing for
the enumerators in the field. Is there any thoughts on why this is
happening?
A short video is attached for fun viewing!
thanks,
Neil
We came up with a solution, though I don't know why it works.
If your choices have data_value integers, the highlight disappears.
yn_dk 1 Yes yn_dk 2 No yn_dk 9 Don't Know
If you change these to a text value, or just append an underscore, the
radio button highlights work just fine.
yn_dk _1 Yes yn_dk _2 No yn_dk _9 Don't Know
So, it's a solution, though It's a mysterious one. I'm sure there is more
to it, but I'm at a loss to better explain it.
~Neil
ยทยทยท
On Sat, Apr 4, 2015 at 4:05 PM Neil Hendrick wrote:
Hi Mitch,
Just to confirm -- that is with the rev 126 release (the one downloadable
from the site)?
Yes, it's 126
We haven't seen that in our testing but have seen other focus-highlight
issues.
OK, any solution?
Are you using the async database prompts on this page that I pointed you
to?
I'm not. I'm pretty far down this road already and didn't want to make
foundation changes to a very large and complex form. Is it necessary?
Ah, OK. Glad you solved the problem. This is the correct solution at this
point in time.
ยทยทยท
-----
We are working on 'select_one_int' and 'select_multiple_int' widgets to
allow people to use numeric values. Until then, using numeric values is
definitely a gotcha.
On the choices sheet, to support arbitrary data types, if you enter a
numeric value, it will be retained as a numeric value (unlike in ODK
Collect). We do very little processing of the sheet content and try to
preserve data types.
The problem is that javascript '==' is very liberal, so we needed to use
'===' for comparisons within the select prompt implementation, and, in that
context, 1 '!==' "1". So the tranformations of your field choices into and
out of the (numeric) representation in the database fails to find a
matching radiobutton value upon redrawing the UI (because those values are
text values in the UI), so the saved choice is removed from the set of
chosen values when the screen is refreshed.
We came up with a solution, though I don't know why it works.
If your choices have data_value integers, the highlight disappears.
yn_dk 1 Yes yn_dk 2 No yn_dk 9 Don't Know
If you change these to a text value, or just append an underscore, the
radio button highlights work just fine.
yn_dk _1 Yes yn_dk _2 No yn_dk _9 Don't Know
So, it's a solution, though It's a mysterious one. I'm sure there is more
to it, but I'm at a loss to better explain it.
I am working on a form in odk 2 and I have the same problem with select_one question. when the user select one choice it doesn't show the selected choice but the value is storing in table. it is really confusing for the user and also when we have an incomplete form and want to complete it for the second time. you can't see the choices in the select_one question.
is it a bug in odk or have any solution?
ODK Survey should populate your selection, both after a selection is made and in an incomplete form. There might be a bug in Survey that's preventing the selection from being populated, could you upload your form so we can see what's the problem?