Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | Next revisionBoth sides next revision |
en:create:inputs-custom [06.01.2015 20:53] – [Limitations] alexander.ritter | en:create:inputs-custom [15.01.2015 19:59] – alexander.ritter |
---|
* Enter a value in your form element and click on "Next". If you now click on the debug information (yellow corner at the top right of the page), there should be a note that the selected/entered value was stored. | * Enter a value in your form element and click on "Next". If you now click on the debug information (yellow corner at the top right of the page), there should be a note that the selected/entered value was stored. |
| |
If you program more sophisticated input elements -- e.g. with JavaScript and/or Flash -- then, as a rule, you need to have hidden input fields to store the measured/collected values (see [[:de:create:break-counter|Note when Browser Window Changes]]). | If you program more sophisticated input elements -- e.g. with JavaScript and/or Flash -- then, as a rule, you need to have hidden input fields to store the measured/collected values (see [[:en:create:break-counter|Note when Browser Window Changes]]). |
| |
In this instance, do __not__ use the PHP function ''prepare_input()''; drag the "internal variables" question type directly into the questionnaire page instead. This generates hidden input fields in the questionnaire (''%%<input type="hidden">%%'') automatically, and their values can be changed using JavaScript. The HTML ID of the input field corresponds to the item ID. | In this instance, do __not__ use the PHP function ''prepare_input()''; drag the "internal variables" question type directly into the questionnaire page instead. This generates hidden input fields in the questionnaire (''%%<input type="hidden">%%'') automatically, and their values can be changed using JavaScript. The HTML ID of the input field corresponds to the item ID. |