I see you connected with my teammate, Mark, in a support case. In the meantime, I'm interested to see if others in the E-Learning Heroes community have some ideas on how to achieve this!
When motion path animations were introduced in Storyline 2, I did a similar interaction, see the 4th example here (because of the conversion to SL360, the formatting is a bit off, but it still illustrates the concept) : https://dev.keypointlearn.com/xcl74_SL360/Animations/story.html. The four navigation buttons control variables, based on their values I could determine the ball's position. And based on the position, I enabled/disabled the applicable nav buttons.
The demo has a full-screen grid that allows the user to always go up, down, left, or right -- until they reach the edge. That makes it relatively easy to control.
In your case, Patrick, if you keep the current design of the "streets," the programming would get much more complicated. So you might want to simplify the layout.
Or even consider changing how the entire interaction works. I'm not sure exactly what you're trying to accomplish with this interaction. Why should a user have to click multiple times to get to the different "addresses"? If there will be content associated with each spot, you could just have the user click each spot to show its content. Extra clicks just to show content aren't going to help them learn more. I think the users are more likely to get frustrated.
7 Replies
Hi Patrick,
Thanks for reaching out!
I see you connected with my teammate, Mark, in a support case. In the meantime, I'm interested to see if others in the E-Learning Heroes community have some ideas on how to achieve this!
When motion path animations were introduced in Storyline 2, I did a similar interaction, see the 4th example here (because of the conversion to SL360, the formatting is a bit off, but it still illustrates the concept) : https://dev.keypointlearn.com/xcl74_SL360/Animations/story.html. The four navigation buttons control variables, based on their values I could determine the ball's position. And based on the position, I enabled/disabled the applicable nav buttons.
Hello Michel, can you share your .story file so that I can understand
Thanks for your help or show me on the attached file
thanks in advance
This old blog post here still has a downloadable source file.
This post was removed by the author
I found the file but I have trouble understanding the principle!
What do the values of the Mazehorizontal and Mazevertical variables correspond to?
Can someone explain?
I created the following a few years ago to demonstrate and explain how to keep motion paths from advancing off the slide:
TIP: Prevent Motion Paths from Moving Off Screen - Articulate Storyline Discussions - E-Learning Heroes
The demo has a full-screen grid that allows the user to always go up, down, left, or right -- until they reach the edge. That makes it relatively easy to control.
In your case, Patrick, if you keep the current design of the "streets," the programming would get much more complicated. So you might want to simplify the layout.
Or even consider changing how the entire interaction works. I'm not sure exactly what you're trying to accomplish with this interaction. Why should a user have to click multiple times to get to the different "addresses"? If there will be content associated with each spot, you could just have the user click each spot to show its content. Extra clicks just to show content aren't going to help them learn more. I think the users are more likely to get frustrated.