Hi, folks. I've attached a section of a project that's not working properly. Hover is working on the objects on the main menu, but I'm not getting the Visited state to work yet. I've got a variable change at the end of scene 2 that I thought would do it. Any ideas would be gratefully appreciated. Thank you! Cheryl
remove the hover trigger...when you have one of the SL inbuilt states SL knows automatically what to do unless you have conditions on it (like with pic 1 and the variable) - but the action to change to hover when you hover is a given. These not required triggers can sometimes cause issues.
I removed it and the pic 1 changes to visited state. Let me know how you go.
Easiest thing to do is to copy your Visited state for the image to a custom state (I called it Complete), and then change the trigger to set the image state to Complete when the variable is true.
I think that since Visited is a built-in state, it has set parameters that maybe were overriding your trigger.
In any case, I tried it with a custom state, and it worked fine.
Am I ever challenged. So even though I "built" these myself - different from a button, for example - it is considered a built in state. I probably was told this before and didn't connect it.
Thank you both so much. Taking notes and I won't forget it! Thank you, thank you, thank you.
Oh - one more thing. My base layer is set to resume saved state. I'd think I would want that because that's the whole reason behind having a visited state. Say that someone went through a scene, came back to that menu, and then decided to immediately do it again. I'm then seeing the hover state overlap the visited which looks odd. Any ideas on that part of it? Thanks!
That does work, but looking at the module, it seems Cheryl wants to mark only after completion of the section. Given that the Visited state will automatically get triggered upon the object being clicked, that would mean that returning to the menu without completing a section would still show as complete.
if you create a shape it has a normal state. If you then add any of the inbuilt states - which are listed here - they all have their own inbuilt actions so you don't need to trigger them to assume that state - unless as I said above, you want to add conditions to it.
Here is a tutorial that may help you with what the states mean.
She has the visited state locked with a condition using the variable which only gets triggered when the scene is complete? doesn't she - sorry I've deleted the file.
It is true that the variable is being used to trigger the state change, but I tested it, and just going in one screen, and then returning to the menu, the Visited state was still shown, as it was triggered automatically by having clicked on it. I don't know if one can lock out the action of a built-in state. You could add more triggers to change the state back to Normal if the variable is not set to true, but that seems like extra work as opposed to having a custom state.
I wanted to close this discussion and say thank you for the help. I changed all the states from Visited to Complete and placed a trigger to change the variable to true on the last slide of each scene. Then I put triggers to change the state of objects on the main menu to Complete if variable = true.
I really appreciate your help. It's so frustrating when you only get an hour here and there to build courses. It feels like I'm forgetting everything I've learned because my job is so fragmented with LMS management, reporting, on and on.
12 Replies
Hi Cheryl
remove the hover trigger...when you have one of the SL inbuilt states SL knows automatically what to do unless you have conditions on it (like with pic 1 and the variable) - but the action to change to hover when you hover is a given. These not required triggers can sometimes cause issues.
I removed it and the pic 1 changes to visited state. Let me know how you go.
Hi Cheryl,
Easiest thing to do is to copy your Visited state for the image to a custom state (I called it Complete), and then change the trigger to set the image state to Complete when the variable is true.
I think that since Visited is a built-in state, it has set parameters that maybe were overriding your trigger.
In any case, I tried it with a custom state, and it worked fine.
Am I ever challenged. So even though I "built" these myself - different from a button, for example - it is considered a built in state. I probably was told this before and didn't connect it.
Thank you both so much. Taking notes and I won't forget it! Thank you, thank you, thank you.
Oh - one more thing. My base layer is set to resume saved state. I'd think I would want that because that's the whole reason behind having a visited state. Say that someone went through a scene, came back to that menu, and then decided to immediately do it again. I'm then seeing the hover state overlap the visited which looks odd. Any ideas on that part of it? Thanks!
Wendy,
That does work, but looking at the module, it seems Cheryl wants to mark only after completion of the section. Given that the Visited state will automatically get triggered upon the object being clicked, that would mean that returning to the menu without completing a section would still show as complete.
Hi Cheryl
if you create a shape it has a normal state. If you then add any of the inbuilt states - which are listed here - they all have their own inbuilt actions so you don't need to trigger them to assume that state - unless as I said above, you want to add conditions to it.
Here is a tutorial that may help you with what the states mean.
Hope that helps
She has the visited state locked with a condition using the variable which only gets triggered when the scene is complete? doesn't she - sorry I've deleted the file.
It is true that the variable is being used to trigger the state change, but I tested it, and just going in one screen, and then returning to the menu, the Visited state was still shown, as it was triggered automatically by having clicked on it. I don't know if one can lock out the action of a built-in state. You could add more triggers to change the state back to Normal if the variable is not set to true, but that seems like extra work as opposed to having a custom state.
I did have a trigger at the end of each scene.
I'm going to spend a few minutes testing and see how it goes. I'll be back!
Yep you're right David - early morning here in Australia and I've been on an webinar since 3am... ;-(
Yes, duplicate the visited state, called it Completed and add the variable condition.
I wanted to close this discussion and say thank you for the help. I changed all the states from Visited to Complete and placed a trigger to change the variable to true on the last slide of each scene. Then I put triggers to change the state of objects on the main menu to Complete if variable = true.
I really appreciate your help. It's so frustrating when you only get an hour here and there to build courses. It feels like I'm forgetting everything I've learned because my job is so fragmented with LMS management, reporting, on and on.
Have a great week!
What great news, Cheryl! And thanks so much for sharing an update on what did the trick for you, as I am sure it will help others in the future!
This discussion is closed. You can start a new discussion or contact Articulate Support.