Forum Discussion
Display Incorrect Selections of Pick Many Free Form
Hello!
I created a pick many freeform question in which I would like either the text or text box outline to change state when the learner selects/doesn't select the correct option, but only AFTER clicking "Submit." Basically, I want the incorrect answers pointed out to the learner on the "Try Again" layer. How can I accomplish this?
Thanks!
You can add triggers to the Try Again that change the state of base-level objects. Use trigger conditions to control the state change.
Personally, I think it's better for the user (as well as easier to program) if the base object has both correct and incorrect custom states.
- I see you added a Drop Incorrect state to the text boxes. That's a built-in state with special functionality for drag-and-drop interactions. Since this is a multi-response question, I think it's better to just use custom states.
For example, here's what a trigger would look like when the correct answer is to select both the Reflexic and Areflexic buttons:
And here's a trigger when the correct answer is to select only one of those buttons:
Notes:
- The condition for a button that shouldn't be chosen is "≠ Selected" (does not equal Selected). Use that instead of "=Normal," because all of the built-in states are based on Normal.
- The conditions check whether the user answered correctly. If so, the text box changes to the correct state. The "Else" statement means the text box will change to the incorrect state if the user doesn't answer correctly.
I added those 2 triggers (for the first two items in the KC) to the attached file. Obviously, there needs to be a trigger for each text box that needs to change.
It’s worth the effort to learn about variables and trigger conditions, because they provide the real power in Storyline. Here’s more information:
- This post provides an overview of variables. It also links to numerous resources. The Value of Variables | Articulate - Community
- The User Guide articles about triggers include some about conditions. Storyline 360: Working with Triggers | Articulate - Community
By the way, I noticed that you used a whole lotta spaces to make the text appear beyond where the buttons are. And that requires soft returns and more spaces when there are 2 lines of text. That's completely unnecessary, and the extra spacing isn't good for screen readers.
Instead, you can simply adjust the Margins of the text box. For example, here's the adjustment I made to the first two text boxes:
To do the same to the other text boxes, I suggest you first edit them to delete the extra spaces and to delete the "Drop Incorrect" state. After you do that, you can use the Format Painter to transfer the settings from one of the updated boxes to the remaining ones.
Finally, thanks for taking the time to prep your file. It really helps when it only includes the necessary file and when objects have meaningful names. 👍
- JudyNolletSuper Hero
You can add triggers to the Try Again that change the state of base-level objects. Use trigger conditions to control the state change.
Personally, I think it's better for the user (as well as easier to program) if the base object has both correct and incorrect custom states.
- I see you added a Drop Incorrect state to the text boxes. That's a built-in state with special functionality for drag-and-drop interactions. Since this is a multi-response question, I think it's better to just use custom states.
For example, here's what a trigger would look like when the correct answer is to select both the Reflexic and Areflexic buttons:
And here's a trigger when the correct answer is to select only one of those buttons:
Notes:
- The condition for a button that shouldn't be chosen is "≠ Selected" (does not equal Selected). Use that instead of "=Normal," because all of the built-in states are based on Normal.
- The conditions check whether the user answered correctly. If so, the text box changes to the correct state. The "Else" statement means the text box will change to the incorrect state if the user doesn't answer correctly.
I added those 2 triggers (for the first two items in the KC) to the attached file. Obviously, there needs to be a trigger for each text box that needs to change.
It’s worth the effort to learn about variables and trigger conditions, because they provide the real power in Storyline. Here’s more information:
- This post provides an overview of variables. It also links to numerous resources. The Value of Variables | Articulate - Community
- The User Guide articles about triggers include some about conditions. Storyline 360: Working with Triggers | Articulate - Community
By the way, I noticed that you used a whole lotta spaces to make the text appear beyond where the buttons are. And that requires soft returns and more spaces when there are 2 lines of text. That's completely unnecessary, and the extra spacing isn't good for screen readers.
Instead, you can simply adjust the Margins of the text box. For example, here's the adjustment I made to the first two text boxes:
To do the same to the other text boxes, I suggest you first edit them to delete the extra spaces and to delete the "Drop Incorrect" state. After you do that, you can use the Format Painter to transfer the settings from one of the updated boxes to the remaining ones.
Finally, thanks for taking the time to prep your file. It really helps when it only includes the necessary file and when objects have meaningful names. 👍
- VickyLinder-23bCommunity Member
Well, I feel a little silly! I had triggers in place, but they weren't working the way I wanted because my when statement was, "When user clicks on..." Sometimes you just need a fresh set of eyes. Thank you!
- JudyNolletSuper Hero
You're welcome! Pay it forward when you can. And best wishes with your projects.