-
Tim Hunt authored
This affects the subquestions that appear as an embedded text input box. There are three cases: 1. Input for subq left blank 2. Input for subq was wrong, and matched by a * wildcard. 3. Input for subq was wrong, and did not match any answer. 2. and 3. should look identical, apart from any feedback in case 2. 1. is different. The state should be displayed as "Not answered" even though the mark for this part is still shown as 0. There are some new unit tests for these cases. Also, we slighly improve handling of , for decimal point in multianswer, although there are still issues. While working on this, I made some minor clean-ups in shortanswer and numerical qtypes.
b2a79cc1