The slider controls look really complex. Why do we have to create multiple states?
Surely it would have been better to set the first and last and then have Storyline work out the in between states? e.g. height, width, transparency, etc. That's how it works in ZebraZapps! Seems like too much hard work to bother with what should be a game changing killer function...
The slider is really awesome, but I think Ed's point is that you have to create states for the object the slider controls. So in the example you post, the slider changes the cost bar to state 26, which assumes the author made at least 26 states for the cost bar....Unless there's something I'm missing and there's a way to create keyframes and have Storyline interpolate what happens in between.
It is a great addition however you need to create each state and a trigger for each state. This is fine if you have a simple slider but like the example in the video there were32 states to create for each of the 3 bars = creating 96 states. Then 96 triggers to create to make them work. That is a LOT of work.
I'm glad the slider functionality is in and will certainly be buying Storyline 2 - It looks like a great product, but the workflow could be improved.
It is a great addition however you need to create each state and a trigger for each state. This is fine if you have a simple slider but like the example in the video there were32 states to create for each of the 3 bars = creating 96 states. Then 96 triggers to create to make them work. That is a LOT of work.
I'm glad the slider functionality is in and will certainly be buying Storyline 2 - It looks like a great product, but the workflow could be improved.
I don't think that video is the best example of how a slider works, the design of the slider is really quite elegant and that example could have been made much more easily than that.
Thanks for the feedback! I am wondering on the triggers you set to scroll back and forth such as the clock. What triggers are set to where you can scroll back and forth without it cancelling each other? What is it triggered by ; is what I am asking I guess.
I'm trying create a slider to show the components of a process flow diagram. The initial state of the images I have set to "hidden" and when I set the trigger to "normal". It doesn't work. The process only has seven components to it.
I'm trying create a slider to show the components of a process flow diagram. The initial state of the images I have set to "hidden" and when I set the trigger to "normal". It doesn't work. The process only has seven components to it.
Any thoughts???
Thanks,
Jodi
Can you share your .story file here so that we can have a closer look?
See attached a revised file. You had set the slider Step option (that specifies the step 'size') to 6. I also set the Start and Initial options to 0. Now the slider works. I wasn't sure if you want to hide items again as you drag the slider back to the left.
You could add more triggers that hide bits of the diagram, depending on the slider variable value or (that's what I would do) create an image object with custom states (each state shows the diagram in different states of completion) and then change the state of this object based on the slider variable.
16 Replies
Actually, the slider controls couldn`t be simpler to use! See here for a tutorial. See here for some examples.
The slider is really awesome, but I think Ed's point is that you have to create states for the object the slider controls. So in the example you post, the slider changes the cost bar to state 26, which assumes the author made at least 26 states for the cost bar....Unless there's something I'm missing and there's a way to create keyframes and have Storyline interpolate what happens in between.
Hi Michael,
It is a great addition however you need to create each state and a trigger for each state. This is fine if you have a simple slider but like the example in the video there were 32 states to create for each of the 3 bars = creating 96 states. Then 96 triggers to create to make them work. That is a LOT of work.
I'm glad the slider functionality is in and will certainly be buying Storyline 2 - It looks like a great product, but the workflow could be improved.
I don't think that video is the best example of how a slider works, the design of the slider is really quite elegant and that example could have been made much more easily than that.
Thanks Michael,
This was really helpful. I was able to create a simple slider using this tutorial. I love this new feature!
Hi Mark! Glad that this thread was able to assist you as well.
This post was removed by the author
Here is the direct link to the examples I had posted a long time ago: http://dev.keypointlearn.com/xcl73_SL2/Sliders/V1/story.html
Thanks for popping in to share the link Michael.
Thanks for the feedback! I am wondering on the triggers you set to scroll back and forth such as the clock. What triggers are set to where you can scroll back and forth without it cancelling each other? What is it triggered by ; is what I am asking I guess.
States seem to work here
Hello,
I'm trying create a slider to show the components of a process flow diagram. The initial state of the images I have set to "hidden" and when I set the trigger to "normal". It doesn't work. The process only has seven components to it.
Any thoughts???
Thanks,
Jodi
Can you share your .story file here so that we can have a closer look?
Hi Michael,
Here's the final as requested. Thanks for taking a look at it for me.
See attached a revised file. You had set the slider Step option (that specifies the step 'size') to 6. I also set the Start and Initial options to 0. Now the slider works. I wasn't sure if you want to hide items again as you drag the slider back to the left.
Thank you so much, very helpful! How do you hide items again to drag the slider back to the left?
You could add more triggers that hide bits of the diagram, depending on the slider variable value or (that's what I would do) create an image object with custom states (each state shows the diagram in different states of completion) and then change the state of this object based on the slider variable.
Thanks for you continued assistance Michael :)
This discussion is closed. You can start a new discussion or contact Articulate Support.