I have a question - is there a limited no. of states for an object to work on html5? I did a slider with 48 states and it works fine on swf version but not for the html5.
I still use Storyline 1 because my company hasn't upgraded yet. However, I downloaded the free trial for AS2 and it has great updates! We are supposed to upgrade this week, so I am quite excited about it because I can add even more functionality to my gamification projects. I hope you can upgrade soon as well!
Thanks for the link. The examples shared did not indicate if its working for html5. The slider I created works fine for the flash version - very smooth sliding - but not the html5 version. The max that I've managed to get it to work for html5 ranges from 5 to 9 states and depending on the size of the images used. I had to split the states into a few layers/objects. Thanks.
If you're using Storyline 1, there isn't a slider feature - so I'm not sure we're clear on your set up. I have successfully used Storyline 2 sliders within the HTML5 output and you'll want to make sure that if you're testing the HTML5 in Storyline 1 you're viewing in one of the supported browsers here, and here for Storyline 2.
Rais, my advice is to keep both up and running. I always start with SL1 and only convert when I know my client has SL2 and needs some advanced features.
Cool that you were able to set it up using SL1 and drag over objects. I know there were a number of fixes and updates in Storyline 2 in regards to how HTML5 content is handled - but Storyline 1 does support HTML5 in those supported browsers. Can you tell us where you were testing it and running into difficulty? It's also worth noting there is a good comparison chart here about Flash, HTML5 and the Mobile player and how features will behave in each.
If you're able to share the .story file, we can take a look at it prior to publishing and check the settings to then see how it'll behave in the intended environment.
Hi Ashley, here's the .story file but its not the latest version as I'm not at work now. Thanks.
Just to add - I tested on chrome and safari. Both had same issue with the states. Or could it be that the problem is with the drag over trigger for html5?
Thanks Rais - it's a lot of triggers you've got there! I took a look and published it here (that goes direct to HTML5 output) and the first slide worked in Chrome for me. I could drag the item along the bottom. The second slide was a bit more finicky but I'm not sure where to begin on all these triggers. It's definitely a cool set up you've got working there - did slide 1 work for you as it did for me? If so, then I'd look at building off of that one, as it's likely something within the trigger/states you're using on the second slide.
Thanks Ashley, yes it works - Awesome! The second slide should work too as it has the same setup but in a circular formation simulating a crank. I managed to get the second slide working smoothly in another file. Strange thing is, for slide one, it is basically the same as the second example (S1template-Flip output) and that output works fine in html5 for me when I published it. Where did I go wrong for slide 1 slider? Did you add/change anything before publishing? If you did not change anything, is it the way I published it?
I didn't change a thing, just published and uploaded. I'm not sure that I'd have time this week to go through all those triggers - but I suspect if it's set up the same way and works in another file, there is one element off on that slide which is causing the difficulty.
Oh, also being on the latest update? No that there was a fix necessarily connected to this issue - but always good practice. :-)
19 Replies
Hi Rais
using both - depends what the client has.
Hi Rais! We still support both as well :)
Hi Wendy, hi Leslie!
I have a question - is there a limited no. of states for an object to work on html5? I did a slider with 48 states and it works fine on swf version but not for the html5.
Thx.
Hi Rais!
We do not have a documented maximum, but I know we had a user here that felt as if the max out was about 100, so seems like yours should work.
Hi Rais,
I still use Storyline 1 because my company hasn't upgraded yet. However, I downloaded the free trial for AS2 and it has great updates! We are supposed to upgrade this week, so I am quite excited about it because I can add even more functionality to my gamification projects. I hope you can upgrade soon as well!
Glad you got to download the trial and let us know if you need additional help once you've officially started!
Hi Leslie,
Thanks for the link. The examples shared did not indicate if its working for html5. The slider I created works fine for the flash version - very smooth sliding - but not the html5 version. The max that I've managed to get it to work for html5 ranges from 5 to 9 states and depending on the size of the images used. I had to split the states into a few layers/objects. Thanks.
Hi Brian,
Good on ya mate! Am hoping to have ours upgraded soon. I've tried SL2 when it was first launched and yes awesome features!
Hi Rais,
If you're using Storyline 1, there isn't a slider feature - so I'm not sure we're clear on your set up. I have successfully used Storyline 2 sliders within the HTML5 output and you'll want to make sure that if you're testing the HTML5 in Storyline 1 you're viewing in one of the supported browsers here, and here for Storyline 2.
I'll keep my eyes open on that Rais. Thanks for sharing and glad you were able to get it working for your needs.
Hi Ashley,
Yes there isn't a slider feature in SL1 but I managed to create one using drag over triggers. Please see attached. Thanks.
Rais, my advice is to keep both up and running. I always start with SL1 and only convert when I know my client has SL2 and needs some advanced features.
I usually use SL2 for HTML5 targeted publish.
Cool adaption on the Slider.
Hi Ryan. Thanks for the advice - will keep that in mind. Glad to know that SL2 publish a more stable html5 version. Awesome!
Hi Rais,
Cool that you were able to set it up using SL1 and drag over objects. I know there were a number of fixes and updates in Storyline 2 in regards to how HTML5 content is handled - but Storyline 1 does support HTML5 in those supported browsers. Can you tell us where you were testing it and running into difficulty? It's also worth noting there is a good comparison chart here about Flash, HTML5 and the Mobile player and how features will behave in each.
If you're able to share the .story file, we can take a look at it prior to publishing and check the settings to then see how it'll behave in the intended environment.
Hi Ashley, here's the .story file but its not the latest version as I'm not at work now. Thanks.
Just to add - I tested on chrome and safari. Both had same issue with the states. Or could it be that the problem is with the drag over trigger for html5?
Thanks Rais - it's a lot of triggers you've got there! I took a look and published it here (that goes direct to HTML5 output) and the first slide worked in Chrome for me. I could drag the item along the bottom. The second slide was a bit more finicky but I'm not sure where to begin on all these triggers. It's definitely a cool set up you've got working there - did slide 1 work for you as it did for me? If so, then I'd look at building off of that one, as it's likely something within the trigger/states you're using on the second slide.
Drag over triggers are supported in the HTML5 output as you can see here.
Thanks Ashley, yes it works - Awesome! The second slide should work too as it has the same setup but in a circular formation simulating a crank. I managed to get the second slide working smoothly in another file. Strange thing is, for slide one, it is basically the same as the second example (S1template-Flip output) and that output works fine in html5 for me when I published it. Where did I go wrong for slide 1 slider? Did you add/change anything before publishing? If you did not change anything, is it the way I published it?
Thanks Ashley
Hi Rais,
I didn't change a thing, just published and uploaded. I'm not sure that I'd have time this week to go through all those triggers - but I suspect if it's set up the same way and works in another file, there is one element off on that slide which is causing the difficulty.
Oh, also being on the latest update? No that there was a fix necessarily connected to this issue - but always good practice. :-)
Hi Ashley,
No worries and thanks for looking into this. Cheers!
This discussion is closed. You can start a new discussion or contact Articulate Support.