Digital Workshop

Hi

I'm working on a Flex pub and can't get the scoring totals to work properly in runtime. When I preview in the editor, the score total works correctly, but not in runtime.

I wonder if this is a function of Flex and Flash.

The set up is as follows:

The viewer takes a quiz in which they are shown an image and need to select the correct item portrayed by the image from 7 choices. Using a standard Opus action, each answer, whether right or wrong, is scored: add (+) 1 to SCORE_TOTAL. This captures every try, right or wrong.

On the scoring page, after the 7 questions on 7 pages, a script is as follows (variable <totalaa> has been added as a variable in pub properties):

var totalaa = 7/SCORE_TOTAL

and the variable <totalaa>% is displayed on the scoring page.

The math seems correct: 7, or the actual number of correct answers, divided by the total number of attempts to answer should equal the percent correct. (If a Forum colleague with better math skills suggests a better formula, I would also be grateful, since math is not my strong suit.)

As mentioned, all works well in preview mode, but in runtime, using either the SWF file or the HTML file, created by the Flex pub, the score always equals 0%, no matter how one answers, or how many times they choose.

Any help would be appreciated.

Kind Regards,

I tried this in a publication.



Without the multiplying by a 100 I get a result of 1. With that line it works as it shoulds.

Perhaps this helps you?

Hi

Thanks for your reply.

I'm afraid I had already done that and failed to include it:

var totalaa = 7/(SCORE_TOTAL)*100

and then my next action is to round total.

Sorry that I left that out, but it doesn't seem to be the issue, since in preview I get the correct total %. I've tested it alot.

The issue is that it won't work in runtime, when I view the actual SWF or HTML file created from Flex. (I have the latest flash player, and Firefox Mozilla on my desktop.)

I wonder if Flex can't manage this extra script or the new variable, like the <totalaa> that I've added. Or, maybe I'm creating the variables incorrectly.

Could it have to do with limitations in Flex?

Kind Regards,

Any possible way you could send me the page of your IMP file where this occurs?

Hi

Thank you for your reply and offer to take a look.

I believe I've figured it out: it seems the trick is not to use the scripting, but rather to stick with Opus standard actions.

So, I eliminated the script, added a "set variable to expression" using the script's expression (7/SCORE_TOTAL)*100, added a "round" action, and it works.

Again, thanks for your support.

Kind Regards,