Next/Previous buttons don't display in quiz review if volume in player settings is off
Hi. I have found a weird bug with the Next and Previous buttons in quiz review related to the volume button.
Background: I have a course and a quiz in separate Storyline 360 files. The quiz consists of customized buttons for submitting each question, and the Next and Previous buttons should not display while the learners take the quiz . However, they should display during quiz review for the learner to navigate among the incorrect questions.
The quiz has no audio, so I have no need for audio controls. I have the seekbar turned off in player settings. However, when I turn off the volume button, the Next and Previous buttons fail to display during quiz review. When I turn the volume button back on, the Next and Previous buttons display as they should. I'd rather not have the volume button display -- it might confuse learners.
I cannot think of a rational reason why the Next and Previous buttons in review mode should be tied to the volume button. I'm certain this is a bug, and have logged a ticket with Articulate: 01817472.
However, the rep I'm working with is trying to get me to fix this by turning on the Next and Previous buttons in the slide properties for each question. I do not want to do this; although the Next button is automatically disabled, the Previous button is not. Our stakeholders for this course do not want learners to navigate to previous questions. I could spend a whole lot of time creating a visited (true/false) variable for each question slide and a trigger that disables the Previous button when the timeline starts, but this creates a very sloppy looking resolution. The question slides display with the Next button automatically disabled, while the Previous button is momentarily "normal," and then switches to "disabled" a few moments later. Not only is this distracting, it is possible to click the Previous button in the couple of seconds it takes for it to become disabled.
Has anyone else experienced this?
I'm sure I'll just have to live with the volume button on there, but why should I have to?
Apologies for my frustration, but I just have to get this off my chest... I shouldn't have to create workarounds and fixes for bugs that Articulate refuses to acknowledge and/or fix. I have submitted several tickets for bugs over the past 16 months that I've been using Storyline, and I have yet to see even one of those bugs get fixed in an update. Instead, I always get the same runaround from reps who never actually read my message or look at my Storyline file until I beg them to. Honestly, it appears that their first reaction is to just send a canned response that insults the user's intelligence ("oh, you just don't have your settings correct"). After a lot of back and forth and explaining what I already said the first time, they finally dig deeper and acknowledge that it's a bug, say "we'll look into it," and then I never hear from them again and the issue is never fixed in an update. I understand that Articulate has to prioritize work, but I don't understand why fixing bugs isn't a higher priority. I have wasted many hours trying to figure out workarounds for issues like this; I'm sure other users do, too. Storyline is a powerful tool, but it could be so much better if Articulate invested time and resources into properly maintaining it.
I'm attaching the file (a mockup) with instructions on the first slide for replicating the issue, in case a staff person or anyone else here cares to look at it. Thank you in advance.