Example
Morph Accordion
I've just now started to play around with the new morph feature, and I'm loving it! When I first started learning how to use Storyline, I wanted to make a traditional accordion interaction. I remember getting very frustrated and consuming many hours dealing with perfect object placement, motion paths and triggers. So, I thought, let's see how the new morph transition could help me. And boy did it! This took me less than an hour, and would have taken less time had I already known what I was doing!
The only issue I'm having is that the Next button appears between slides. If one is quick, it can be clicked and you can move on to the next slide. If anyone knows how I could prevent that from happening, I'd love to know!
Try it out here: Morph Accordion
Source file is available for download below.
6 Replies
So simple and so effective, Thaddaeus. Indeed, the morphing transition takes its time, only then does the slide timeline begin, and finally the “Next” button deactivation trigger works. It takes less than a second, but you can see it. I think the easy solution is... but you already know the easy solution to this. I've been looking for an hour, but we can't manage the player's built-in buttons with triggers, with the exception of “Hide” “Normal”, etc, I think. Maybe with JS code? The case remains open.
Ah ah ah! I fixed it, ThaddaeusSmith ! OK, this is really-really just for the fun of solving a puzzle before I go to bed later than planned, because the not-so-complicated solution isn't simple enough to implement in a real module, just to avoid the Next button display problem. Check out the Review link attached. I hid the Side Menu at the start because the solution is visible in it. After that, it's just more triggers from yours. Would you like to have a look at the .story file? 😄 https://360.articulate.com/review/content/0dac2d24-e80f-4ec2-a598-e2d49b5bd7fc/review
Ah, Thierry! I can always count on you to take on a challenge and successfully solve it! It looks like you made a second scene, and the slide in the first scene (which does not have a Next button), jumps to the corresponding slide in the second scene (which does have a Next button) if that slide is the last one to be visited. Is that right?
You're right. Not really practical for a real module, but a solution nonetheless! If I'm correct about how you solved this, no need for the source file. If I'm not, then I'd love to see it!You're absolutely right, Thaddaeus. With a true/false “ALLvisited” variable that drags to the same tab in the second scene if it's true when you click on any tab in the first scene. Problem solved, but the solution is completely useless (story of my life!).
Thanks for suggesting the riddle. I fell asleep with a stupid self-satisfied smile on my face. See you soon.
I have reported this temporary appearance of the Next button (despite a Change State of Next button to Hidden when Timeline Starts trigger) as a possible bug. The work-around is to change the trigger to Change State of Next button to Hidden when Timeline Reaches 0. This worked for me.
Thanks for reporting this, Karen! Yes, it should work the way we'd expect. I like your workaround. I tried it and, only sometimes, the Next button flashes as active. But, it happens very quickly and is less noticeable. Thanks for the work-around!
Getting Started with the E-Learning Challenges
Find practical answers to common questions about the E-Learning Challenges, a weekly event that helps you build skills, create your portfolio, and grow as an e-learning professional.