Motion Paths Triggered by Buttons

Jan 13, 2019

Paula Gutierrez
By Paula Gutierrez

Hi there, 

I am working on an interactive menu, but I am having troubles trying to program the triggers. The initial stage starts with a ball at the top of the slide, while two buttons trigger a motion path either to the middle or to the bottom of the slide.  Depending on the second stage (middle or bottom) two buttons will determine whether the ball should go back to to the top or to the bottom of the slide.  I basically need that for each position where the ball lands the buttons in the layer instruct the learner to go to either one of the remaining options available. I have tried reducing the number of motion paths and trying the Relative Start Point without luck.

I have tried using different layers, but I am very confused and I have created so many layers and several motion paths that this project is becoming unmanageable. I hope there is a more practical way to do this. Any advice is highly appreciated. 

 

4 Replies
Paula Gutierrez
5 years ago02/06/19 at 7:51 pm (UTC)

Hi community, 

I have made some progress, but I am still in need of help trying to figure out how to properly code the conditions so that ball picks up the new motion path form its last location.  the idea is that the user clicks on any of the buttons and that will trigger the ball to move to the top (Triangle button), to the center (Star button), or to the bottom (rectangle button).  I am having problems with combinations where the motion is non-sequential, for example from top to bottom and then to center.  Again, any advice is highly appreciated. 

 

Regards

Ben McKenna
5 years ago02/08/19 at 11:01 am (UTC)

Hi Luis,

Here's what I came up with (review link with .story attached):

https://360.articulate.com/review/content/83d310f9-6bf2-4ceb-9232-534db78a67d1/review
https://articulateusercontent.com/review/uploads/lhNr-FafV7X9jxDO/motion-path-menu.story

I tried to recreate it from scratch because that usually works best for me. Hopefully since it's just the fundamentals you'll be able to follow the logic behind it. Essentially you have:

  • 4x relative motion paths (one space up, one space down, two spaces up, two spaces down)
  • A button set (to keep track of the current selection)
  • Variable to keep track of the previous selection
  • Triggers to fire the correct motion path based on the number of spaces between the previous and current selection

I used relative motion paths to achieve this, but that's not the only way to do it. Needless to say if you want to change the menu layout or add more sections to navigate to, you will need to accommodate for those as well (your .story file can get very complex very fast!)

Hopefully this is what you were looking for - let me know if there were any additional functionalities you needed covered too.

This discussion is closed. You can start a new discussion or contact Articulate Support.