This question pops up over and over again, so i made a new post i can point to whenever someone asks about this.
\n
For Storyline360, either in your published folder or in the Programme folder find the slides.min.js file.
(C:\\Program Files (x86)\\Articulate\\360\\Storyline\\player\\unified\\html5\\lib\\scripts)
\n
What i did was unminifying the file...so it becomes what more readable
Used this here... https://unminify.com/
\n
I added several console.log(\"now this happens\") to the slides.min.js to figure out where what happened exactly and thus soon found that there are several functions in it that cause the playbutton on mobiles.
\n
onMobileStart
createMobileStartOverlay
showMobileStartOverlay
killMobileStartOverlay
\n
All quite promising...so could i just call one of these functions ?
\n
After several tests and retry's i found that just adding
this.onStart(); at the end of the onMobileStart function overrides the play button and mobile behaves as desired.
\n
So this is onMobileStart inside slides.min.js
\n
onMobileStart: function (t) {
var e,
n = this;
(this.rejectDeferred = t.rejectDeferred),
o.addClass(document.body, \"resume-shown\"),
(e = { visible: !0 }),
t.mobileStartAsPrompt && (e.isResumePrompt = !0),
this.setState(e, function () {
var t = null != n.refs.resume ? n.refs.resume : n.refs.playIcon;
c.env.is360 || t.focus(), l.trigger(u.startOverlay.READY);
});
this.onStart();
},
\n
Adding my slides.min.js file for anyone to test it with. Make sure though to copy and save your original one somewhere, so in case of troubles you can go back. Also keep in mind that whenever Articulate updates Storyline this file will be updated too, and you need to do the procedure above again.
DO NOT copy and replace the slides.min.js file with this one after updates...because Articulate might have changed things...so not advised using an older file. Redo the steps and change your own slides.min.js file.
This question pops up over and over again, so i made a new post i can point to whenever someone asks about this.
\n
For Storyline360, either in your published folder or in the Programme folder find the slides.min.js file.
(C:\\Program Files (x86)\\Articulate\\360\\Storyline\\player\\unified\\html5\\lib\\scripts)
\n
What i did was unminifying the file...so it becomes what more readable
Used this here... https://unminify.com/
\n
I added several console.log(\"now this happens\") to the slides.min.js to figure out where what happened exactly and thus soon found that there are several functions in it that cause the playbutton on mobiles.
\n
onMobileStart
createMobileStartOverlay
showMobileStartOverlay
killMobileStartOverlay
\n
All quite promising...so could i just call one of these functions ?
\n
After several tests and retry's i found that just adding
this.onStart(); at the end of the onMobileStart function overrides the play button and mobile behaves as desired.
\n
So this is onMobileStart inside slides.min.js
\n
onMobileStart: function (t) {
var e,
n = this;
(this.rejectDeferred = t.rejectDeferred),
o.addClass(document.body, \"resume-shown\"),
(e = { visible: !0 }),
t.mobileStartAsPrompt && (e.isResumePrompt = !0),
this.setState(e, function () {
var t = null != n.refs.resume ? n.refs.resume : n.refs.playIcon;
c.env.is360 || t.focus(), l.trigger(u.startOverlay.READY);
});
this.onStart();
},
\n
Adding my slides.min.js file for anyone to test it with. Make sure though to copy and save your original one somewhere, so in case of troubles you can go back. Also keep in mind that whenever Articulate updates Storyline this file will be updated too, and you need to do the procedure above again.
DO NOT copy and replace the slides.min.js file with this one after updates...because Articulate might have changed things...so not advised using an older file. Redo the steps and change your own slides.min.js file.
This is super cool, Math! Haven't tried it yet, but thanks so much for sharing!
Looking forward to giving it a try. Great job.
Bookmarked this, baby - thanks!
Yeah in some posts i mentioned that Articulate engineers should check this out.
I didnot test it on all browsers/devices. In fact i have to do it then after each update, might do it when we get a new update and test it on all browsers/devices.
As Articulate just updated Storyline360 i changed and updated my slides.min.js file and just tested it on Review and on TalentLMS. Worked fine there, no 'Big bad black button of Despair' .
\n
Adding the latest file here so anyone wanted can test with this one. As i solely work with the Modern Player, its for the unified folder.
Hi Math,
\n
Can you please help as I have this issue with one of my courses?
\n
would you provide step by step process of how I do the above as I have never done this before?
\n
many thanks in advance.
\n
scott
\n
Aint the steps above clear enough ?
\n
Offcourse i help. First question... are you using Storyline360 or Storyline3. Because they differ.
Kind regards,
Math
Thank you Math 🙏
\n
\n
I am using Storyline 360 to create the video and assessment slides and then uploading them into a Rise 360 course I am creating.
Ok, SL360 is easiest to explain . I will make a step-by-step approach for it. Do keep in mind that for uploading to Rise you do need to edit the Programme files folder as you directly publish to Review.
Thank you Math that's amazing. Would you also please explain how to edit the Programme files folder in the step by step instructions?
Hi Math,
\n
do you have a idea to make the resume button bigger? Our clients are people with disabilities so they need a bigger \"resume button\": Any thouhgts?
\n
(S360).
\n
\n
Thanks in advance!
Yeah you probably can target it with JS and CSS. I will check it either this evening or tomorrow when i have some time to spare.
