"To understand recursion, you must first understand recursion." - Unknown Zen Master
Thanks for reporting this bug. I am working on the fix and plan to release an update as soon as possible.
-Sean
Dave:I think it would be great to have separate properties for accessing response 'options' and 'optionvalues'. Specifying numerical '/ optionvalues' is great for data recording and analysis, but if you want to give participants feedback on some of their choices, a numerical value sometimes isn't what you want. To clarify:<radiobuttons q1>/ caption="Who was the first president of the United States:"/ options=("George Washington", "Abraham Lincoln", "Thomas Jefferson")</radiobuttons>In this case <% radiobuttons.q1.response %> will give you "George Washington" (at least if the participant is reasonably smart...). But when setting<radiobuttons q1>/ caption="Who was the first president of the United States:"/ options=("George Washington", "Abraham Lincoln", "Thomas Jefferson")/ optionvalues=("1", "2", "3")</radiobuttons> <% radiobuttons.q1.response %> will give you "1" with no (easy) way to retrieve the original response text "George Washington". I'd basically like to have both options at all times via different properties such as <% radiobuttons.q1.response %> for the response text and <% radiobuttons.q1.responsevalue %> for the associated numerical value.
Hi Dave,
Great suggestion, I think the value is obvious. Currently, there are "option" and "optionvalue" properties that allow you to access each option by index. You could write an expression that compares the response to each of the values and returns the matching one. Needless to say, that's a bit cumbersome.
I could see two new properties - "responsetext" and "responsevalue" - that return the caption and the underlying value assigned to the response respectively. Not difficult to add, I'll try to get this into the next update.
seandr: You could write an expression that compares the response to each of the values and returns the matching one.