Text Button Doesn't Change State to 'Visited'
Jun 29, 2020
Hi,
I've set up a menu page that has several links (all text) to different parts of my course. The first link has a 'Normal' and 'Visited' state, and I've setup triggers to cause the text to enter a 'Visited' state once clicked. The 'Visited' state is the same as the normal state visually except for a strikethrough running through the text (to create the effect it's been 'crossed off'). The next (and every subsequent link) has three states - 'Normal', 'Visited' and 'Disabled'. Once the first link enters a 'Visited' state, a trigger is setup so the next link should switch from 'Disabled' to Normal. When they click on it, it should then enter a 'Visited' state, and the effect cascades as the user continues the course.
The problem I have is that the first link will not change to 'Visited' after it's been clicked. I believe the triggers are setup correctly, the software just doesn't do the intended action. I have another save file where instead of the text boxes being the links to each part of the course, I had an icon next to each word that acted as a button that would trigger navigation to the next slide in the course. The triggers and states are setup identically save for the fact these icons are what the user interacts with instead of the text boxes themselves, and this seemed to work perfectly.
Is there an issue with using text boxes in trigger conditions? Is it something to do with my use of strikethrough as the visual effect on the 'Visited' state? Any help would be very much appreciated! See attached for a screenshot of my trigger setup.
5 Replies
Hi Ethan!
I'm excited to help! It sounds like it might be an error with a trigger but I'd love to see the file to determine the right fix. Would you mind attaching your file? You can use the Add Attachment in this discussion. If you prefer to share it privately, use this upload link.
After taking a look at the file, I'll report back with a fix! Let me know if you have additional questions.
You don't need a trigger to change to visited so you can delete that.
I can see you are jumping slides so and triggers after a jump to trigger will fail so you need to move these above the jump to slide. For the listed state to be remembered you will need to set the slide to resume saved state. As it is a menu you should ideally be using a custom state as visited just means clicked and a user could press the first trigger and then jump back to the menu to see the next section.
Thanks both for your replies.
I had this working on a previous iteration of the same project, the only difference being I used icons instead of the text boxes themselves as the buttons that would navigate to each slide. So I'm hung up on this because I know it works haha! The change to 'Visited' is important as it enables the next link on the menu. Any means to navigate back and forth freely without the use of these links will be removed once the project is ready for publishing.
@Lauren I have submitted a copy of my file as it is for my employer and contains assets I would not wish to share publicly. :)
Thanks again to both you.
If it worked before using icons, it was because you were lucky. Creating a trigger to do the functions of the built-in triggers (change to 'Visited" state) is always risky, as your triggers can conflict with the built-in magic. The results can sometimes be spectacular, but are almost always unpredictable and unuseful. If you have to use "Visited" state, use the built-in actions, and remember, as Phil said, all it means is "This has been clicked". From your description, you may want to use a custom state (lots of us use "Completed"), and then create your own triggers, which gives you better control.
Agree with Walt I think you probably fluked the order of the triggers.
If the navigation is important you need to use a custom state rather than visited and use variables to rack the completion.
This discussion is closed. You can start a new discussion or contact Articulate Support.