Forum Discussion
Change state of button from Javascript?
I think, as is often the case, after a couple of days of fiddling and talking about these problems, I come back to intending to never using buttons again. I keep falling into the trap of using their shorthands when fleshing out ideas and then trying to fix the shortcomings - rather than just building things directly. So much of my interfaces is now built on javascript/gsap/css hacks injected to address Storyline shortcomings that I start to wonder if it's the right tool for me anymore. But it integrates better with Rise - and I use that integration a lot.
That all said, when you have to build certain interactions like "Show layer X when the state of these 5 buttons is all Visited, unless condition Y has already occurred", and the state of some of those buttons only changes after Javascript executes a lookup in a LRS to see if a peice of data exists, then I have to juggle watched variables to trigger the state changes. This is when I wish I could just change object states directly from javascript. And then I step back and say "Why am I making this so complicated?"
I wish there was an Articualte technical community forum.
- MathNotermans-96 months agoCommunity Member
Completely agree with you....and i seldom use default buttons in my projects. Most of the times make them as i want/need them from images or SVGs.
As i donot use Rise due to lack of flexibility in Rise, at some point i switched to Lectora. Similar problems exist in that tool, but alltogether i prefer it above Storyline. Combo of Javascript/GSAP/CSS and several third party JS-libraries makes switching back and forth between Lectora and Storyline for projects not too hard. Biggest difference is the element selectors and SVG implementation.