Button and Audio Triggers not working properly.

Mar 28, 2019

I am currently having issues with two courses.  I have a couple of slides that link to lightbox slides or standalone slides and I put a trigger to stop the audio if the user clicks on any of the buttons on the base layer so the audio does not continue to play when they return (assuming we will have folks who jump ahead without listening to the full audio).  This has always worked in the past. So I'm not sure why it's not working now.

Here's what I've tried:

  • I have set up triggers to stop audio when user clicks on any of the buttons on the screen.  
  • I have changed the base layer to resume saved state when returning and auto decide as well (no change)

I'm also having the issue where I have buttons to three modules on a slide.  I want to restrict the user from clicking modules out of sequence.  That is not working with the way I have it set up either.

Here's what I've tried:

  • A trigger to disable the button with the condition "If mod1complete is not equal to true"
  • A trigger to disable the button with the condition "If mod1complete is equal to false"

Neither of those trigger/variables are working for me either.  Again, this has worked in the past, so not sure why it's not working now.


Any help with this would be much appreciated!  Thanks.

1 Reply
Crystal Horn

Hi Nicole! I had a look at the Specialist file, and for the audio, I see two issues:

  • Trigger order: Triggers fire in the order they're listed. If you have a trigger to jump to another slide as the first trigger on an object, the other triggers won't have a chance to fire.

    Slide 1.4 shows the lightboxes before stopping the audio. I changed the audio trigger to come first, and now the audio seems to be working as expected after closing the lightbox.
  • Bug: We have a bug where stopping the audio on a slide, navigating away from the slide, and then returning to the slide to resume the saved state will cause the audio to pick up where it left off. Slide 1.6 is showing this behavior when you navigate to Modules 1 or 2 and then return to 1.6.

    The only workaround is to start the audio with a button so that it will remain stopped when returning to the slide, and I'm not sure that really works with your design. I'll keep this discussion updated about the status of this bug.

For the module navigation challenge, do you want to disable Module 2 until Module 1 has been completed?  Here's what I did:

  • Set the initial state of the Module 2 button to disabled. That way, you won't need a trigger to disable this button when the timeline starts.
  • Added a trigger to change the state of Module 2 button to Normal when the timeline starts IF mod1complete variable is true.
  • I deleted the triggers to change states to Visited. Visited is a built-in state, and objects change to this state automatically once they've been clicked.

I'm attaching your Specialist file with these changes. Let me know how it works for you!

This discussion is closed. You can start a new discussion or contact Articulate Support.