Storyline buttons states on iPad
Mar 03, 2020
I built an interaction in Storyline that I'm plugging into a Rise course. Works great on a computer. When I tried on an iPad (about 50% of our users), I noticed that all the Storyline buttons have to be tapped twice. One tap to reveal selected state and a second tap to execute the trigger.
There's an easy workaround. I can just put a hotspot over the button and assign the same trigger. Or I could build a button without any states, presumably.
But I feel like I'm missing something here. I would think the default buttons in Storyline would work on an iPad without this adjustment. My workaround also loses the state on a computer, which I'd prefer to have. What am I not understanding? I like using the default buttons in SL. But now I think I have to cover the 50+ buttons with a hotspot. Doh!
Because I'm plugging into Rise, I can't have user get accustomed to a double tapping a button since they've been single tapping buttons on the iPad prior to arriving at the interaction.
Would appreciate input from someone with more experience here. Thanks
5 Replies
Hi Michael!
You've provided great details for us to start troubleshooting! Thank you!
I'm interested in if you've tried viewing just the Storyline course on a mobile device, and seeing the same issues with the states. Also, are you using the Modern Player rather than the Classic Player?
Lastly, would you mind sharing your file so I can test it on my end? We don't have this logged as a bug so I want to make sure we can get to the bottom of it! You can either share your file as an attachment in this discussion, or you can share it privately using this link. Either way, you'll hear back from me when I find the fix.
Hi Lauren. Thanks for the timely follow up. Answers to your questions:
---Get same problem if look at it only in Review 360 on an iPad. I haven't output as HTML and posted to a web server, though, or output directly as SCORM and popped into my LMS. Short on time today, but will do later if you think it will help with analysis.
---Using Modern Player with "Menus and Controls" set to off.
---If you have an iPad handy, you should able to replicate the problem and see for yourself:
https://360.articulate.com/review/content/4a0d0abf-8b1f-47b5-b694-e398ba8ef0bb/review
Posting file now. Appreciate the help. Mike
PS: Removing states from the buttons solves the problem.
I am having this same issue when testing my course on an iPad. Thanks for your workaround, Mike!
Hi Bethany. Lauren at Articulate got back to me and responded directly via email. Very nice of them to look at my file and send a response. That's what I like about Articulate. Not sure why nothing was posted here.
As suspected, the root cause is the default button states. It's the "down" state not the "selected" state causing the problem. I was corrected by them in my correspondence which was pretty funny.
Their recommended solution was to remove the button states. That wasn't what I was asking for in my query. I was asking whether there was a setting to adjust other than create a work-around.
The answer to that, at this time, is no, as far as I can tell.
Going forward, I am now making a single-state custom button with at the beginning of the project that I copy into subsequent slides.
****HOWEVER, be careful because if you just cut-and-past, and don't paste using the source-location formatting, I believe it will add the states back to the button. I've seen the states reintroduced in subsequent slides and assume that was the root cause. So make sure you select the "special" paste with source formatting.*********
Drives me batty when I see the states again when all I've been doing is pasting a button I made already. I have not tested this systematically as the cause. But definitely seeing states reintroduced in subsequent slides. Not a problem when you can place a single button on the slide master, but I usually can't do that with many projects.
Hi Michael,
Thanks for popping back in to share the solution with Bethany.
It looks like you continued your conversation with Lauren in a support case, which is why it was not posted here to the public forum thread :)
This discussion is closed. You can start a new discussion or contact Articulate Support.