I wonder if anyone else is having issues with Slider interactions (Storyline 360) not working on Touch-Enabled desktop monitors? For example, we have employees with Dell desktops and touch-enabled monitors. Slider interactions work fine when using the mouse but they don't move at all when trying with the touch screen. Perhaps this is a limitation of touch-enabled monitors?
Thanks for reaching out and sharing what you are seeing in your course.
As mentioned in the thread that Matthew shared above, the computer will still display the desktop view and gestures will not work the same as a mobile environment.
We have a document on supported touchscreen gestures here and it is limited to tablets and smartphones.
I do know that others have mentioned more need for flexibility since many computers use a touch screen feature now as well as many tablets have computing power. I invite you to share your thoughts and use-case with our team here as we track these requests.
I wonder if it is possible (through some customisation of the published project code perhaps) to 'force' the web browser on a touch enabled device to load the Storyline project in the Responsive Player built for mobiles?
I am experiencing the same issue as Scott with Windows Surface Pro tablets. No issues if the keyboard is connected in order to use the touchpad, but without a keyboard relying on the touchscreen key features such as slider, dials etc do not work on any browser.
Not ideal however if we need the project to perform this way across multiple devices all of the time.
I can see in Storyline's published story_html5.html file that there are checks taking place on the User Agent in order to tell Storyline what to do if the device is a mobile for example. This codebase is unfortunately quite cryptic and I can't clearly see how it can be manipulated to remove the checks and just force the Responsive Player.
3 Replies
Hello Scott,
Thanks for reaching out and sharing what you are seeing in your course.
As mentioned in the thread that Matthew shared above, the computer will still display the desktop view and gestures will not work the same as a mobile environment.
We have a document on supported touchscreen gestures here and it is limited to tablets and smartphones.
I do know that others have mentioned more need for flexibility since many computers use a touch screen feature now as well as many tablets have computing power. I invite you to share your thoughts and use-case with our team here as we track these requests.
Hi Leslie,
I wonder if it is possible (through some customisation of the published project code perhaps) to 'force' the web browser on a touch enabled device to load the Storyline project in the Responsive Player built for mobiles?
I am experiencing the same issue as Scott with Windows Surface Pro tablets. No issues if the keyboard is connected in order to use the touchpad, but without a keyboard relying on the touchscreen key features such as slider, dials etc do not work on any browser.
Through my research today I have discovered that it is possible using Chrome's in-built developer tools to manually change the defined 'User Agent' before loading a site, which if we set as iPhone for example will load the Storyline project in the Responsive Player. More details here for people interested: https://www.howtogeek.com/113439/how-to-change-your-browsers-user-agent-without-installing-any-extensions/
Not ideal however if we need the project to perform this way across multiple devices all of the time.
I can see in Storyline's published story_html5.html file that there are checks taking place on the User Agent in order to tell Storyline what to do if the device is a mobile for example. This codebase is unfortunately quite cryptic and I can't clearly see how it can be manipulated to remove the checks and just force the Responsive Player.
I'd really appreciate any help.
Hi Chris!
Good q! I bet others have similar questions regarding altering the coding to make more touchscreen gestures included in the Responsive Player output.
As of now, this is not a practice we support. It looks like you've put time into researching this topic, and we appreciate you sharing it with us!
I hope our brilliant community members, who might've already tried to do this, can share their tips and tricks!
This discussion is closed. You can start a new discussion or contact Articulate Support.