Resize the Storyline Player.

Hi Blake,

Not sure you're gonna be able to find a way to make the course only downsize when launched. You could submit a feature request for that. I think your best options at this time would probably be to Display at user's current browser size or Resize browser to optimal size. Here's more on that.

Does anyone know if this feature now exists in 360?

Im after almost exactly the same thing - to allow the player window to scale smaller, but to stop it scaling larger (and therefore making all the graphics look fuzzy and nasty)

If this isnt an option now, then does anyone have a hack or workaround that could give a similar ability?

Many thanks.

Hi Andrew, 

Digging up an old discussion on this one, wow!  I haven't seen a lot of other requests similar to Blake's in my time here - there isn't a way to control it based not allowing it to go larger. Within Storyline 360 though what you will see is our new responsive player, so that if they do choose to view on a smaller device we're going to resize it down as displayed here. 

This is an old discussion.  But I would still love this feature.  I think the responsive player would work for me.  My fingers are crossed that it is included in SL3.

Responsive player will be something you get with Storyline 3 too! All the features you see today in Storyline 360 such as html5 only or first output, responsive player, etc. will be available to you in Storyline 3! 

Thanks for the replies Ashley, but this last one worries me.

I thought Storyline 360 was Storyline 3 and that the "60" part referred to it being such a step up from previous versions it warranted something more than just "3" (ie, the HTML5, responsiveness, and annual subscription model)

Im now concerned that Ive just bought my 360 subscription only to find out that its not the latest version and that something bigger and better is coming?!

P.S. you also mentioned in another post about the need to update my SL version (thanks for that) but I'll reply to that here as it fits in with what we are discussing now.... is there anywhere that we as professional developers who rely on SL can get proper information on updates, point releases and new features?

Im finding it hard to stay on top of actual information rather than conjecture. Thanks for the help.

Oh no, Andrew! I don't mean to worry you at all! Let me try to break it down a bit further, and if you have other questions don't hesitate to ask here or connect with our Success team! They're pros at describing the differences. 

Storyline 360 and Storyline 3 are separate products. Storyline 360 is just one tool in the larger suite of tools available to you as a part of Articulate 360 (Rise, Content Library, Articulate Review, etc.) It's also a subscription service - whereas Storyline 3 follows our standard perpetual license model (meaning you buy a license once, and it's yours for good). 

So what does this mean for your Storyline 360 tool? You're still going to get updates, fixes and all the new things, and based on the subscription model those are actually released a bit quicker as we're able to push them out to you on a more frequent basis - vs. a perpetual model where we release large groups of fixes all at once. Take a look at the Storyline version history for Storyline 2 and compare it to Storyline 360 so far.  So what you'll see is 11 updates in 2 years, and Storyline 360 has been updated 4 times in 4 months. Plus, all the fixes and features you're getting in other Articulate 360 tools! 

As for information about the updates, Articulate 360 should be prompting you to install the updates when you open the desktop tray app as long as you're connected to the internet. If you're not seeing that, and you didn't disable them, can you connect with our Support engineers?  We're also publishing the Releases note (such as the ones linked above) with every update and we're sharing some big news here (like when closed captioning was released!) in ELH as a forum post or as a part of the "What's new" page.

Phew! That's a lot to digest, I know...I've had to do it myself! So let me know if you need anything else, or have any other worries! 

Thats great info Ashley, thank you very much.

My tray app is disabled and I just start Storyline directly so thats probably why Ive been missing all this. I'll be sure to get that fixed thanks.

Im a bit worried that Storyline 360 and 3 are separate products. This can only mean that the devs now need to support two distinct and different SL versions from the time when SL3 is released.

When SL3 is released, then everyone like myself who bought a 360 subscription just to get the latest version of SL will now be stuck on that subscription, but using a divergent tool to the main one. Seems a very odd way of operating.

Thanks again for the help though - very clear.

I'll check out that version history checklist; looks like just the sort of thing I was after.

Hi Andrew,

I wouldn't say that you're stuck or using a tool other than the main one. I think one of the biggest values in Articulate 360 comes from the fact that we're able to release updates and fixes much quicker to the subscription products (such as Storyline 360) than we are to our standalone perpetual products (the future Storyline 3, and existing Storyline 2). So although Storyline 3 will be released after Articulate 360 was initially released, they'll both continue to grow and evolve, and Storyline 360 will be doing so at a higher rate of speed based on the subscription set up. 

Hopefully once Storyline 3 is released this will be a bit clearer as you'll be able to do a trial of that as well, and experience any differences between Articulate 360 and Storyline 3 standalone. 

Hi there, 

I feel your pain about the resize course. Find my solo discussion: 

https://community.articulate.com/discussions/articulate-storyline/flexible-player-browser-setting

As a matter of fact, CSS3 has a markup for exactly this behavior. How to implement it is yet to be worked. 

Time is short on my side to test... We are on the edge waiting for SL3 and hoping it will be fixed like soooo many other stuff.

SUBMIT A FEATURE REQUEST!

I'm looking for exactly the same thing - to allow the player window to scale smaller than a specified size, but stop scaling it up to a specified size (original size of the course). 

Hi Xavier, 

There isn't a built in way to do that in Storyline, the settings detailed here for Storyline 2 will allow it to scale the player and/or browser based on the size of the course or the size of the browser. 

If you'd like to investigate the custom options talked about here, you may also want to reach out to the individual users here! I'm not sure if they're subscribed here, as the post is a bit older - but you could always use the "contact me" button on a ELH users' profile to reach out to them directly!

Best of luck with your project! 

It's pretty sad because we are pretty much stuck... Some of our learners have a very small screen so our courses need to adapt but other parts of our learners have a very big screen and the content to read and see since it's all fuzzy.

I'm trying to find a solution on my own and for anyone who's interested here's what I found up to now:

The scaling is achieved with the "transform: scale();" propriety that is added when you select the "Scale player to fill browser window" in the setting's player. The value is updated by the javascript depending on the size of the screen as you can see in this video (put it full screen it's small):

I found the problem but not the solution, I couldn't find a way to set a kind of "max-width" to this "transform: scale();" propriety. It would need to stop at "transform: scale(1);" so it doesn't get bigger than the original size of the course. Maybe someone will find a solution.

Nice detective work Xavier.

If that transform.scale() property is set by JS, can we set it at runtime ourselves to change the player size from within a SL course?

If so, then I could maybe code up the necessary algorithm.

That would be amazing! 

Just found out how to do it.

https://community.articulate.com/discussions/articulate-storyline/a-better-responsive-player

Super Xavier!

Test driving in a couple of days!

Hello amazing community,

I have a project that I would like to embed using an iframe into a Wordpress page.  The client wants the project to be long and sit on the length of the page.  The javascript above looks promising for an answer.  I want to set the width to fill the screen, but not the length if that makes sense.  If my project is 960 pixels X 1770 pixels.  I would like the width to be exactly 960 or to scale to fill, but not have the length considered.  Does anyone have any ideas?

Thanks :)