Forum Discussion
Enabling Custom and Player Next Buttons
Hey Everyone- This is the second time I am coming for advice and expertise on Storyline 360 next button functionality (though, this time it is a different issue). I think we are quickly becoming foe...
A few notes:
- All the triggers that change buttons to Disabled will also run again if the user returns to the slide. As I said before, instead of triggers, you could simply set the Initial State to Disabled.
- I can't tell why things freeze if a previous-layer button is clicked while the current layer is playing. State-changing triggers shouldn't cause that. It might be an issue with all the audio. It might be an issue with the properties. Since that's "unexpected behavior," I suggest you contact the support staff: https://access.articulate.com/support/contact
- Personally, I'd use Dialog layers, and add a copy of the necessary graphic(s) on each layer.
- If you have additional issues, you should start a new discussion.
Hey Judy-
Thanks for the consist help on the discussion boards! You are always a huge help.
Yeah, I can't change the format of the button states for some reason, or I would have made them visibly different.
When you say, "on each layer, hide those semi-transparent shapes when the timeline ends", am I just removing the "show until end" feature for each semi-transparent shape and leaving a bit of space between the end of the timeline and the shapes?
There are different ways to get rid of an object when the timeline ends.
Yes, you can adjust how long they show on the timeline. Or give them an Exit animation; that would run at the end of the object's timeline. Or use a trigger (though that's probably more complex than needed, unless the hiding needs conditions).
Another option I neglected to mention above: use Dialog layers. They work similar to lightboxes in that they prevent the user from interacting with anything except what's on the layer. They do require a close-layer trigger, either attached to a button or that runs when the timeline ends.
By the way, you can insert objects directly into the state of another object. So, for example, you could insert a small checkmark in the Visited state. Or insert something else that sets it apart.
Also, be aware that transparent parts of an image aren't clickable. For example, when I was previewing your file, it seemed like I couldn't click directly on the numbers; I had to click on the colored circles. That could be quite frustrating for users. Here's more info about that issue: TIP: Making icons easier to program and easier to click | Articulate - Community
Personally, I wouldn't use images for those buttons. Instead, they could be circles with the numbers entered directly into the shapes. Those would be very easy to edit so they'd look different for different states.
FYI: I edited my original comment to provide a different solution. Why? I hadn't thought about accessibility.
Yes, a semi-transparent over a button will prevent a user from clicking/tapping the button. But it won't prevent someone from using the button with a keyboard.
