In my feature request you'll find links to threads around this topic with a few workarounds.
bugs.limesurvey.org/view.php?id=12088
But to apply this "semi mandatory" behavior to a lot of questions seems to be impossible.
Surveydesigners which are already aware of these concepts will use other tools, since if you have to design adhoc surveys you won't get the additional amount of workarounds payed.
In other tools you just change this behavior with one click.
If you design one survey for eternity it might be possible to get away with workarounds.
In my idea workarounds are absolutely not valueless, but they do tend to be forgotten, since finding them back here at the forum is sometimes not easy. I think that there is a need for a database of documented (and tested) workarounds, with the versions that they work on and with example questions/groups/surveys.
I would not mind working on such a solution, together with others.
Tammo
Tammo ter Hark at Respondage
For Limesurvey reporting, education and customized themes
respondage.nl
Without workarounds a lot of stuff couldn't be done in Limesurvey. So I think the workarounds are VERY valuable. If something is a very rare case, workarounds can help to get to something that probably will never make it to core, because it is not worth it implenting, because only very few need it. So the possibility of workarounds are great.
However, if certain workarounds are in a high demand, they should move from workaround to core. Especially that "normal" users often are not able to implement workarounds (no access to the template, no possibility to use Javascript, etc).
Help us to help you!
Provide your LS version and where it is installed (own server, uni/employer, SaaS hosting, etc.).
Always provide a LSS file (not LSQ or LSG).
Note: I answer at this forum in my spare time, I'm not a LimeSurvey GmbH employee.