Participant

Question

Variables not consistently producing accurate click counts

Forum|Forum|6 years ago
December 2, 2019
3 replies
876 views

Hello,

HELP! We have been using captivate to simulate medical software workflows for 2 years successfully. We have recently ventured into the idea of using projects to test end users workflows (performance based exams). We are using different variables to count correct and incorrect clicks. Each time we run through the simulation we are getting different results (counts). 50% of the time we reach the expected outcome, the other 50% it is incorrect, and out of those wrong outcomes , the same scenario being tested is producing different results. We have checked the advanced actions and variables multiple times for accuracy. we are at a wits end! We are assuming that there is something broken with captivate itself because our logic seems to be flawless. Does anyone have any experience with this type of logic?

Thank you.

This topic has been closed for replies.

TLCMediaDesign

Inspiring

I think you are going to need to explain/show your logic in more detail.

In my experience, incrementing variables can result in the issue you are describing. Anytime there is a click you would need to disable each option (correct/incorrect) on the slide. Otherwise they can click either more than once. When you are checking your results, see if the total of incorrect and correct is more than the number of interactions you are evaluating.

L

LinzHAuthor

Participant

The count for correct/incorrect clicks seems to be accurate, but the complete/incomplete task result is not accurate. Here is an example of the test cases we ran yesterday, only the .... the combo in green were the only accurate outcomes (task3 state).

Here is the what the variables looks like for Test 2. The count of wrong choices is correct, the state of task 3 in correct, however, the variable on the task 3 completiong is incorrect. It should say ' You're a dope' (this is just a sample, we do not call out end users dopes;) .

L

LinzHAuthor

Participant

The issue seems to be with counting variables= 0. It only produces the correct result if the fake click incrementing variables=1. We need to count missed clicks = 0 as well, and have the outcome dependant on that incremented value regardless of false click results.

Stagprime2687219

Legend

Another strategy I would offer is that when I make a project designed to test a very specific sequence - there is typically one pathway I need them to go.

I create a variable called step which will track the number of the current step the learner should be on in the process.

If they click anything other than the correct button I might increment my mistake variable otherwise if they are correct, I will increment my step variable.

So I have lots of logic that checks every step for the conditions of right and wrong.

if (step==1) yada this

if (step==2) yada that

L

LinzHAuthor

Participant

Thanks for the tips. We arent using order of steps logic. We just want to make sure they click on each tasks and if not clicked mark it incorrect(mistake). So we have two variables wrongchoice(not clicked) and correct choice. We dont care about the order they perform the clicks in. So we have multiple advanced actions jumping slides.

Stagprime2687219

Legend

If you are also doing a bunch of slide jumping - you'll want two SmartShapes with your two variables on each slide so you can see them whatever slide you go to. You could just set them to Rest of Project, I suppose.

Again - just watch the variables for whatever choice you make - they should increment accordingly - if they don't - you know the specific click where it broke.

Also - sequence of operations makes a difference in some cases. The logic may look complete but an action that happens before or after another one could be undoing something.

An example I offer is where I might say that if a variable is equal to 0 we show something and make the variable equal to one. but if my very next statement says that if the variable equals 1 to hide something and make the variable equal to 0 - both will have fired and it will look like nothing happened. The reverse would be true as well.

What I am saying is that the logic may look sound when each step is taken in isolation but when partnered with other actions could generate conflict. That is how the troubleshooting boxes can make a big difference in tracking things down.

Stagprime2687219

Legend

I have also created a project to track the number of mistakes that a user makes.

Without more detail - this is tough to answer but let me offer a tip.

A troubleshooting trick that I use frequently, is to create a SmartShape to display the variable in question such as

$$myVariable$$.

Place that on the display and start clicking through your project. Watch the variable change for each click where you expect it to and when it does not. If I suspect a variable is not updating the way it is supposed to, this will help to pinpoint where the logic is breaking.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded