Allow operations within Conditionals
May 4, 2009 12:00 AM
I just discovered a flaw in the Conditional tab. Well, perhaps it's intentional, but it is a problem for developers who are accustomed to doing math while doing comparisons.
I tried to do an action IF Counter >= 6*VAR(Multiplier). Unfortunately, the action fired only if Counter was at least 6, regardless of the value of Multiplier (which sometimes brought Counter far below 6).
I performed other tests and learned that if I enter 6*2, then the system treated it as a 6, and if I enter 2*6, then the system treated it as a 2. It seems that Lectora ignores everything past the first number. No warning message pops up that arithmetic operations are not allowed there.
So, I would like to see operations being allowed here. It would be an extra step to define a new variable.
At the very least, if the operation cannot be allowed, then include a warning message when a developer attempts to enter this information. It is very intuitive for devs to enter operations in a conditional, and if there is nothing to warn them against that, then they open themselves to a whole book of frustrating errors that they cannot explain.
KevinI just discovered a flaw in the Conditional tab. Well, perhaps it's intentional, but it is a problem for developers who are accustomed to doing math while doing comparisons.
I tried to do an action IF Counter >= 6*VAR(Multiplier). Unfortunately, the action fired only if Counter was at least 6, regardless of the value of Multiplier (which sometimes brought Counter far below 6).
I performed other tests and learned that if I enter 6*2, then the system treated it as a 6, and if I enter 2*6, then the system treated it as a 2. It seems that Lectora ignores everything past the first number. No warning message pops up that arithmetic operations are not allowed there.
So, I would like to see operations being allowed here. It would be an extra step to define a new variable.
At the very least, if the operation cannot be allowed, then include a warning message when a developer attempts to enter this information. It is very intuitive for devs to enter operations in a conditional, and if there is nothing to warn them against that, then they open themselves to a whole book of frustrating errors that they cannot explain.
Kevin
Discussions have been disabled for this post