RANT: Changing behavior of the Next button in Presenter/Engage '13
I'm beyond frustrated right now. I'm explained this through support and filled out a "feature request," but perhaps someone can explain the logic behind Articulate's decision to completely change how the Next button functions (in an Engage '13 interaction) all of a sudden?
I had been using an Engage interaction in our courses as a "help" file in the topbar right (near the Exit button) - it described to the user what the player buttons mean, how to navigate through the course, etc.). Every course had it. it's optional...like an FAQ almost.
However, in upgrading to Presenter '13, this functionality got all glitchy and didn't work correctly, so I was forced to make this slide part of standard course content (as a PPT slide). That meant also redoing my standard template in Storyline, s well - so both template interfaces would match. Needless to say, it took some work.
Fast forward to today - I had to upgrade a presenter '09 course to '13 and add in the new Engage interaction. After realizing the Next/Previous buttons seemed to be turned off by default (huh?), I added them in and published the course.
However, when I get to the Engage interaction and click next, I don't go to the next slide--you know, like I would any other time EVER that I click the Next button in an Articulate course. Instead, it goes to the next little pop-up in my labeled graphic interaction. Huh? I click Next again - same thing. I have to click 10 times to get through these items before it finishes and goes to the next page.
OK...I can see why someone *might* want to force the user to see everything in the interaction. But there is no way to turn this off. None. WHAT? WHY? Why would this not only be the default action, but the ONLY action? It seems completely ridiculous to me.
Articulate Support's workaround (ah, our favorite word!) is that the user should just go to the menu on the left to advance the slide. But if I wanted to users to advance through the course using the menu, I wouldn't be using the Next button, which has ALWAYS performed the same way...until now. Why am I being forced to make the users jump around the screen to go to the next page?
As far as I'm concerned, course navigation should be consistent and not create confusion for users. However, this is exactly what has been created with no way to disable it.
I can turn off the Next/Previous buttons in the interaction, but would leave an even more confusing scenario for users used to clicking Next to advance because the buttons are simply not there at all.
The ironies are:
1. I had to rebuild my templates because of a functionality glitch in the upgrade due to this exact interaction, and now the "new" way is even worse.
2. This interaction is to explain course navigation to users, which isn't even accurate anymore because of the behavior this exact slide now exhibits.
Surely I'm not the only one experiencing this issue or having a problem with it, am I? I just don't understand the decision that was made to have this function this way without a way to opt out of it. It really leaves me handcuffed. I do not want to force our users to have to click 10 times (on our interaction) in every course to skip past this slide, or fumble around to a different part of the interface because of this one slide.
Any real ways to get around this?