Interesting potential bug with variables
Jan 07, 2015
By
james lavis
Hey folks,
I've been playing around with storyline and variables, coming from a coding background and working in an environment that uses storyline. Here's what I'm wondering if anyone has noticed, and may be able to shed some light as to why it happens.
My goal is simple, create a button that you can toggle with clicks. Been around the site and tried a number of the examples. So the issue I came across is that if I create a button with a base state (normal), and create a custom state (lit) and change it's appearance, the variable switch will not work. If I use a program provided state like "selected", I can still modify the button and call the change. Why won't a custom state change work and display?
3 Replies
The Selected state is a built-in state that is automatically called and toggled. With a custom button and custom state, you need to use triggers to manually switch between states. See attached a quick example of a standard button with built-in states vs. a custom button with a custom 'Lit' state. Hope that helps.
Hi James
not sure if this is what you mean
Hey Michael that's what I was looking for. I got it working by modifying a provided state to show the button I want, but that's actually easier. It can be quite the trick thinking from coding back to storyline as at times coding is much easier!
This discussion is closed. You can start a new discussion or contact Articulate Support.