In each action, there is the condtion and the Else tab.
Set up the condition, then set the Else action. It might take some playing around, and you might have to actually use more than one action to accomplish one task.
basic one would be:
General:
on: Show
Action: Show
target: TextBox1_right
Condition Tab:
Performa action only if the following true: Checked
variable:question_0001
Relationship: is correct
ELSE:
If the condions are not met.....: Checked
action: Show
Target: TextBox1_wrong
So if the question_0001 is correct it will show the textbox1_true object, if it is not correct, it will show the TextBox1_wrong object.
This is a very basic if/then/else statement, trial and error is always fun though too!
AlexT said:Hello all, I have created a mock-test. This test has the following characterictics: -Part 1 of the test is comprised of test questions that are drawn from a pool of potential questions. -Part 2 of the test is comprised of 1 mandatory question. -Participant answers are always remembered, and can be reviewed at any time. -Participants are allowed to skip over questions, exit the test, and come back to answer the skipped questions later. The issue is the test's “submit” button. Is there a way to de-activate this button until ALL the test questions have been answered? I am getting more comfortable with the creation of custom-made variables, and I am guessing that such variables will be needed in order to find a solution. Thanks for your time, Alex
