Multiple choice

[Alex-Jordan]

This was primarily meant to address #1017, so that now when there is a PopUp and a nonegative integer is declared as the answer, you have the same behavior as with RadioButtons where it is assumed to be an index, even when it matches one of the actual answers. But you can use noindex => 1 to override that.

Several other changes happen too. An HTML option (inside an HTML select) can have value and label attributes. If there is text content inside the option, that is used as the default for the value and label attributes. If both attributes are specified, I think there is no significance to the text children of the option. Anyway, in the manner of @drgrice1's revision to parserRadioButtons in the last release (or the one before?) this now carefully separates the option text, option value, and option label. The details are slightly different owing to how label means something different here. But much of this was copying chunks from parserRadioButtons.pl and then here and there adjusting.

I'm updating the PTX output to be more semantically correct. It will require new things on the PTX side, but that should be OK.

Lastly, I thought it would be convenient to make a parent parserMultipleChoice.pl file to load the four multiple choice macro files we have now.

[pstaabp]

I've been thinking it would be nice to have a replacement for PGchoicemacros.pl for matching problems and has the API's similar to CheckboxList, RadioButtons. Anyway, I would think it could be called parserMultipleChoice.pl, but if we use this filename to pull in all similar macros, it could be parserMatching.pl.

[Alex-Jordan]

There is some discussion of this at #843.

[pstaabp]

Looks good.

[drgrice1]

I think this looks good. I am not sure how useful the values option is for this in general. Perhaps you have a particular usage for PTX in mind with that. The main objective with radio buttons with the values option was to give something more meaningful that can be displayed in the past answers. For popups that isn't really an issue.

One thing that I would like to do with the parserPopUp.pl macro is to stop using a native browser select, and use a javascript implementation. The advantage of doing that would be that you could actually have math equations in the drop down.

[drgrice1]

One other clean up item.

[pstaabp]

I think this looks ready to go now. @drgrice1, ready to merge?

[drgrice1]

Yeah, this can be merged.

[taniwallach]

I added a comment to the release notes about this being a breaking change for some problems.