Storyline NEXT button

Hi Steve

see this thread

http://community.articulate.com/forums/t/57597.aspx

Yes, it appears that 'Restricted' behaviour has changed

Oops forgot to add...

the search function here is not working (Articulate are working on it).

In the meantime you can try using www.Articusearch.com

Thanks Wendy....but now I'm REALLY confused.

Here is a response from the ever-helpful Jonathan when I had this issue occur on another project.

Hi Steve,

Thanks for contacting Articulate Support!

In Articulate Storyline 1, restricted and locked navigation settings only affected the menu. In contrast, the navigation settings in Articulate Storyline 2 affect both the menu and the player buttons, making it much easier to control the overall navigation for your course.

When I asked if it was the case...

"that in Storyline 2 you can never set the layer option

Pause Timeline of Base Layer without hiding that layer(to release the base

timeline) if you want to have a restricted player?"

his response was..

Hi Steve,

Yes it looks like it. It pauses the base layer even ifthat option is not checked. That would be a bug.

By the way, I've reported this to our Quality AssuranceTeam already.

We'll email you if there's an update on this issue.

Regards,

Jonathan Reque

Customer Support Engineer

Articulate Support - http://www.articulate.com/support/

In any event, I am having the situation now where the published course will not progress at all on certain slides.

Hello Steve!

I hope the QA team has an answer for you on this.

In the meantime, you could change the navigation to free temporarily, or you can use a custom next button and disable the player one.

Also in the thread linked above, one member suggested using a blank slide as the base layer as a workaround. Hopefully one of these options will work.

Thanks Emily.  Yes, there are a number or workarounds but it is really time consuming going through what are some very large courses to re-do all of the navigation for Storyline 2 to comply with the client's requirements.  I was just wondering if I'm the only one who has mentioned this issue.

Steve,

I experienced the same thing, and thought I was going to pull every strand of hair off the top of my hair trying to find a solution!  However, over on this thread Jill McNair came up with a pretty quick and easy work around, so I now don't have to worry about going bald!!

Hope this helps.

Bobbi

Oh... and to make this a little more rapid, what I did was

• Click the "duplicate layer" button on the base layer, then with the base layer selected, clicked Ctrl-A to select everything on the base layer and hit delete. 
• Change your timeline length to however long you want it to be before the next button works (I set mine to 0.25 seconds!)
• From the story view, (looking at ALL slides/scenes), I again Ctrl-A, unchecked the next and previous buttons and then re-checked them.  This put the default jump to previous and jump to next triggers back on the base slides.
• On first slide created my trigger to show the newly duplicated layer upon timeline start, then used the copy/paste button to paste it on each of my slides.  After I pasted the trigger, it shows "unassigned" for the layer, but you can easily select that link and then select the newly duplicated layer.

Thanks, Bobbi. Looking at your profile picture it would be an awful shame for you to go bald - but here I'm perhaps being inappropriate (which we often are down here in Australia!).

It looks as though we're not alone in this.  It seems an bad error in logic for this change to have been made in SL2 (but more than made up for by having the autosave function - Yes!!!).  It is self-contradictory to have the NEXT button rely on the base layer timeline completing but also have the layer function option of pausing the base layer timeline!

I also think there is a bug that sometimes prevents the base timeline from ever completing - Support are looking at that  - maybe the bug is picked up when translating an SL1 project into SL2.

Thanks heaps for letting me know I'm not the only one having this issue.

I'll reprint this in your thread.

Steve

Steve,

LOL, thank you and yes, I think it would be a darn shame if I went bald (especially because of silly programmatic design!).  I am truly hoping that this is a bug/flaw in the new version and that Articulate will soon deploy an update or patch to correct this.  

In the meantime, although not pretty nor convenient, I will forge forward with this work-around.

Best of luck to you!

Bobbi

Thank you...and to you.  If anything comes through from Support I'll let you know via this thread.

Steve

Steve,

I think I have come up with a very feasible work-around/solution to this issue! I have detailed it over on this thread.

Hope this helps!

Bobbi

Thanks for sharing Bobbi!