- Posts: 14270
- Thank you received: 4349
Ask the community, share ideas, and connect with other LimeSurvey users!
if ($(thisRow).attr('data-name') != 'clickedRow') { addRow(); $(thisRow).attr('data-name', 'clickedRow'); // if you also want to hide the answered row: $(thisRow).hide(); }
if ($(thisRow).attr('data-name') != 'clickedRow') { $(thisRow).attr('data-name', 'clickedRow'); // if you also want to hide the answered row: $(thisRow).fadeOut(1000); setTimeout(function(){ addRow(); }, 1000); }
Please read the thread contents and look into the .lss files attached. That behaviour is not a "big problem", it is what oksana wanted. That's why I said "I don't like the idea of hiding the rows as they are answered without any indication of the answer because it gives no opportunity to fix mistaken clicks.".However, there is one big problem: If radio button of a subquestion is clicked, you can't see that the radio button is checked. It forwards immediately to the next subquestion. Respondents should see their answer for 500ms before next subquestion is shown.
$(thisRow).hide();
I understood this, that she was concerned about the fact that the subquestion is hidden without visible result of the click.Respondents should see their answer for 500ms before next subquestion is shown.