How clever to to add the triggers in this way so, as you say, they can only be counted once (rather than needing to add extra triggers to subtract). Question: is there a reason you've suggested that Shona create a new "count" state rather than using the visited state in the same sequence? And adding triggers in that order? I'm sure you have a reason, but I can't figure out what it is. Thanks!
I worry with visited that it changes before the triggers fire, I did initially go with visited (started typing visited and then change my initial post) and never demo'd it. If it works off visited then you need one less trigger. I was stuck for time this morning and didnt want to troubleshoot it if it didnt work.
Tx for your reply. I do become bedfuddled sometimes over the firing of the visited state. Anyway, had a chance to go back and try it out, and it seems it DOES work in this instance, and as you said, you can get away with one less trigger.
And I gather the reason is:
SL "knows" about the visited state, it's pre-coded (probably not the right word) and so you don't need to tell it to "change the state to visited when the Learner clicks"...happens automatically,
So, all you need is the add 1 when the user clicks if the state is not equal to...
Love saving triggers. If only I could remember all these tips and tricks when I need them!
8 Replies
I wouldn't use hot spots as they can be counted again. Use transparent shapes with a custom state (counted).
Add a variable number called Count.
On each transparent shape add a trigger to adjust variable count and add 1 on condition state is not equal to counted.
add a second trigger to change the state to counted
Add the triggers in that order this way they can only be counted once
here is a quick demo
I created one shape (not transparent ) set the triggers then duplicated it
Perfect thats all I needed to know thanks very much
Hey Phil,
How clever to to add the triggers in this way so, as you say, they can only be counted once (rather than needing to add extra triggers to subtract). Question: is there a reason you've suggested that Shona create a new "count" state rather than using the visited state in the same sequence? And adding triggers in that order? I'm sure you have a reason, but I can't figure out what it is. Thanks!
Hi Rebecca
I worry with visited that it changes before the triggers fire, I did initially go with visited (started typing visited and then change my initial post) and never demo'd it. If it works off visited then you need one less trigger. I was stuck for time this morning and didnt want to troubleshoot it if it didnt work.
Hi Phil,
Tx for your reply. I do become bedfuddled sometimes over the firing of the visited state. Anyway, had a chance to go back and try it out, and it seems it DOES work in this instance, and as you said, you can get away with one less trigger.
And I gather the reason is:
SL "knows" about the visited state, it's pre-coded (probably not the right word) and so you don't need to tell it to "change the state to visited when the Learner clicks"...happens automatically,
So, all you need is the add 1 when the user clicks if the state is not equal to...
Love saving triggers. If only I could remember all these tips and tricks when I need them!
Hi Rebecca
I tried the visited state instead and it works perfectly also so have decided to use your example as it seemed much easier!
Much much appreciated
Hi Shona,
Glad it worked. And thanks for asking the question, since we both learned from it. Tx again to Phil!
This discussion is closed. You can start a new discussion or contact Articulate Support.