Thanks all - I know that this has been a hot discussion topic for awhile, and I've made it my personal pet project to ensure this gets in front of our team for further discussion. Your continued voices carry a lot of weight - so it's appreciated.
I just realised that this NEW in SL2 Next button restriction was the cause of a major problem with all my SL1 imports. I spent 100's of hours pulling my hair out, not knowing why my navigation wouldn't work. I created my own restrictions in SL1 and created an error when someone clicked NEXT but wasn't done the slide. This SL2 change (unknown to me) broke all my navigation upon import, and I just couldn't figure it out. I lost contracts, missed deadlines... all because of this fundamental change to the software. Have a pop up on the player section that when someone chooses restricted, they are aware that they are also disabling the next button, or put it in disabled mode as suggested here (greyed out). Regardless, at least inform the author/course creator that something has been disabled.
I could fix my imports with code changes after publishing but I've decided to go back and create custom navigation buttons and eliminate the NEXT/PREV. A great deal of work, but I don't want to be a victim again when a programmer decides to make a fundamental change and not inform the user.
Very, very frustrated. Happy I finally found the solution to my problems, but its a problem I should have never had............. and many hours and many hairs that I'll never get back.
I get it Vaughan, and the frustration and venting is entirely valid and I wish it helped. What I hope does help is my commitment to this issue and continuing to discuss it and share the thoughts of other users like you with the rest of our team. I’m also really sorry that I can’t make a firm commitment to resolve this problem. We're careful about testing new updates to make sure we don't put other features at risk, and I don't want to commit to a date before I have any other information. You're in the right place, and we’ll share as much as we can, as soon as we can!
Great news! We just released another update for Articulate 360, and included a few important fixes and new features that you'll see in the release notes here.
The item you may be interested in is how when you restrict or lock navigation, you can now choose whether it impacts just the course menu or also disables the Previous and Next buttons. And you can use triggers to override restricted navigation for individual slides.
Just launch the Articulate 360 desktop app on your computer and click the Update button. Details here.
Please let us know if you have any questions, either here or by reaching out to our Support Engineers directly.
10 Replies
+1
+2
My two cents: don't surprise. Yes, there's a Next. It's just disabled until you do something...
+3
+ 1 seems to make logical sense that the next button should appear to be disabled if you are using restrictive nav.
Thanks all - I know that this has been a hot discussion topic for awhile, and I've made it my personal pet project to ensure this gets in front of our team for further discussion. Your continued voices carry a lot of weight - so it's appreciated.
Agree
Folks, I know this is old but I gota vent.
I just realised that this NEW in SL2 Next button restriction was the cause of a major problem with all my SL1 imports. I spent 100's of hours pulling my hair out, not knowing why my navigation wouldn't work. I created my own restrictions in SL1 and created an error when someone clicked NEXT but wasn't done the slide. This SL2 change (unknown to me) broke all my navigation upon import, and I just couldn't figure it out. I lost contracts, missed deadlines... all because of this fundamental change to the software. Have a pop up on the player section that when someone chooses restricted, they are aware that they are also disabling the next button, or put it in disabled mode as suggested here (greyed out). Regardless, at least inform the author/course creator that something has been disabled.
I could fix my imports with code changes after publishing but I've decided to go back and create custom navigation buttons and eliminate the NEXT/PREV. A great deal of work, but I don't want to be a victim again when a programmer decides to make a fundamental change and not inform the user.
Very, very frustrated. Happy I finally found the solution to my problems, but its a problem I should have never had............. and many hours and many hairs that I'll never get back.
Got my vote.
I get it Vaughan, and the frustration and venting is entirely valid and I wish it helped. What I hope does help is my commitment to this issue and continuing to discuss it and share the thoughts of other users like you with the rest of our team. I’m also really sorry that I can’t make a firm commitment to resolve this problem. We're careful about testing new updates to make sure we don't put other features at risk, and I don't want to commit to a date before I have any other information. You're in the right place, and we’ll share as much as we can, as soon as we can!
Hi all,
Great news! We just released another update for Articulate 360, and included a few important fixes and new features that you'll see in the release notes here.
The item you may be interested in is how when you restrict or lock navigation, you can now choose whether it impacts just the course menu or also disables the Previous and Next buttons. And you can use triggers to override restricted navigation for individual slides.
Just launch the Articulate 360 desktop app on your computer and click the Update button. Details here.
Please let us know if you have any questions, either here or by reaching out to our Support Engineers directly.
Great work Articulate - this will be a very welcome enhancement!
This discussion is closed. You can start a new discussion or contact Articulate Support.