Mazi wrote:
Why do you need a checkbox in front of the text fields if the user has to fill out the fields manually?
Why not simply using an array (text) question type with heading "value for A" and "value for B" and setting the advanced question attributes "numbers only".
This way the user can enter several data sets with A and B values:
docs.limesurvey.org/Question+type+-+Arra...eSurvey#Numbers_only
Thanks, that's very helpful. A reply in two parts:
1. I need a _mixed_ answer: some checkboxes (for the answers we want to put in front of the users) and an array of numerical entry boxes for any different answers which they may dream up. I'm sure that isn't in LimeSurvey at present, but perhaps you might be able to give some advice about how I could hack it up.
2. Interaction with those numerical checkboxes is a delicate issue. I don't think array column headings would do: I'd much rather put a label (like a= or b=) on each box. The reason: we're dealing with complete novices here, and we want to prompt them to do certain things. Making the array lines look like the fixed alternative lines would be a good idea (I think).
2a. As for the checkbox on the numerical-box lines: I see it as a simple way for my subjects to _delete_ an answer they don't want to give. As in my previous post about other-box interaction, I'd like them to type directly into those boxes, see a checkmark immediately and automatically appear, and be able at any stage to uncheck or recheck (without erasing the stuff already typed in).
3. User-interaction design is a delicate and experimental subject (sorry, I'm being professorial

). Apple is rich because Steve Jobs realised this; Linux is hard to use because (most) geeks don't. A solution which seems adequate, to an expert programmer-geek like me or you (I'm presuming ...

) may floor inexperienced users. So 'implement it yourself' may still be the best answer, because I'm not sure about 1, 2 or 2a until I've experimented.
Thanks for your help and advice: I really appreciate it. If there's an easy way to experiment by defining a new question type and coding it up by using bits of two or three existing question types, I'd love to hear.