I have created a seek and find game in SL2 and using variables inserted a counter at the top of the scene. There are ten items to find, so the counter is "You have %varStart% items out of 10 left to find." My problem is if the user double-clicks on an item it throws the count off, counting each click as a found item. Is there any way to either prevent double-click (I did specify in the instructions to single click) or to force the variable to interpret a double-click as a single click? Each item is far enough away from each other as not to overlap the clicks.
Can you set the state of each item to disabled upon a click so that the variable changes on the first click but then it is disabled so the second click of the double click doesn't subtract from the variable?
Another approach (As you may not always want to disable other functionality that is triggered when the object is selected) is to have a true/false variable for each item being counted. On click change the variable to true and have a trigger that when the variable changes to add +1 to the counter variable.
I use this method a lot for system training etc where there may be multiple pop out boxes that I want the user to interact with and they may view multiple times.
3 Replies
Can you set the state of each item to disabled upon a click so that the variable changes on the first click but then it is disabled so the second click of the double click doesn't subtract from the variable?
Thank you Brian! I was not seeing the forest for the trees. Variable and triggers and states...oh my!
Another approach (As you may not always want to disable other functionality that is triggered when the object is selected) is to have a true/false variable for each item being counted. On click change the variable to true and have a trigger that when the variable changes to add +1 to the counter variable.
I use this method a lot for system training etc where there may be multiple pop out boxes that I want the user to interact with and they may view multiple times.
This discussion is closed. You can start a new discussion or contact Articulate Support.