# No longer between two values trigger dilemma

I have a math-heavy course.

Some questions have an answer that needs to be correct to 4 decimal places, but Articulate only works to 2 decimal places.

My work around was to accept answers between two values (or greater than or equal to X and less than or equal to Y).

I set up a trigger that changes the state of a shape if the answer is correct.  If the answer was correct but was then changed to something incorrect, another trigger changes the shape back to its original state.

If the answer is equal to (==) or not equal to (!==), the trigger on the shape works without a problem!

If the answer is between two values, the trigger changes the shape when the answer is correct, but the trigger does not change the shape back to the original if the answer is changed to something incorrect.

I've tried this with both "when variable changes" and "when control loses focus", but the overall effects seem to be the same.

Any ideas how I can get articulate to register when an answer is no longer between two values?

###### 7 Replies Pierre Sosa

but the trigger does not change the shape back to the original if the answer is changed to something incorrect

I sometimes have trouble getting something like this to work if I'm using the built-in "Normal" state as my original state.

An easy workaround that works for me is to duplicate the Normal state and give it a name like "Starting", then I use this new Starting state in my triggers when I want a shape to revert back to the original. So I figured out an alternative!

A correct answer is accepted "between two values"; an incorrect answer is "not equal !=" to the lower value.

Because Articulate only reads to the hundreth's place, 0.01-0.02 can make the answer correct, but any value outside of 0.010 and 0.0199... will satisfy the trigger to make it look like the answer is incorrect. According to articulate, 0.01 and 0.0199... are the same number.