Next Button Hidden / Normal - Not working properly

Apr 26, 2018

I have submitted a ticket on this, but while I'm waiting to hear back from Articulate, I'm wondering if anyone else is experiencing a similar problem and have figured out how to fix it.

I have a branching slide to which learners return after visiting each of the branched slides.  The Next button on the branching slide is hidden when the timeline starts.  Once learners have viewed all branched slides and have returned to the branching slide I have set a trigger for the Next button to Normal when "All of" the branches have been visited.  Two things are happening:

1. MINOR (I can live with it) - the Next button flickers each time the learner returns to the branching slide, then disappears...confusing to the learners...where did the button go.  Looks like something went wrong.

2. MAJOR - the learners are stuck on the branching slide...they can not move to the next section because the next button is missing.

This WAS working - probably before a recent update.  Any ideas of how to finesse this until I hear back from Articulate?  I need to get this course off to the state for approval.  

21 Replies
Bob O'Donnell

Sounds like Tom is helping you out. Your Next button could be set to be "Disabled" instead of hidden, that should eliminate any flicker. Its basically showing up and then going away quickly. If its just disabled the flicker shouldn't be noticeable. Setting the Next button to be "Normal" should be easy to fix using variables or checking the states of your button or objects used to branch the learner.

Tom's demo should cover you.

Susan Stewart

Bob, thanks for jumping in.

I still get the Next button shifting between the Normal coloration and status and the Disabled coloration and status.  I'm afraid our users would be frustrated having a button that is disabled (unusable but still visible).

I must have something wrong with my triggers...but I haven't changed anything on that slide since the last review of the module (when hiding the next button and changing it to normal using triggers and states worked) and the current review.  (I'm looking at the variables tutorials now.  I have used them but on a simple and limited basis with individual guidance.  It is definitely an area in which I need to become proficient.)

Walt Hamilton

Think of variables this way:

Think of your project like telling a story, perhaps you are familiar with plays. Think of a play where the audience gets to vote on what happens at certain points.
The objects you put on the slide are the actors that come onto the stage. (Some people even refer to the visible part of your slide as a stage.)
The triggers are the script that the actors read - "When this happens on the stage, you do this" Example - If a girl says "I love you", answer "I know" if she is your sister, and answer "I love you, too" if she is not your sister. "If she is your sister" and "if she is not your sister" are conditions in the triggers. "Is" is the == (equal) operator, and "is not" is the != (not equal) operator. Operators perform comparisons on objects, states, and values.
When the play pauses during the first act to ask the audience to vote on a future course of action - "Will Leonore save her husband before she is discovered to be a female?", the result of the vote is recorded. Then during the third act, the actors look at the paper recording the vote, and they know which ending to perform. The paper that carries the result of the vote from the first act to the third is a variable.
The script tells the actors, "Read the paper. If the vote is that she is not discovered, perform the original ending." The SL equivalent of this is "Jump to Original Ending when user clicks Next on condition SheWillSaveHerHusband == (is equal to) True (According to the vote in the first act)".

There is a sample at this post that does what it sounds like you want. Warning: it uses custom Next buttons, but if you want to use the built-in buttons you can. Just put NEXT in the trigger for the object that is turned to normal.

Kay Fenton

I too am having problems with the Next button not appearing with a trigger.  I have Next hidden at the start of the timeline, a trigger for each of the slides to be visited, that sets the labels to visited states (which is working) and then once both are visited the Next button should be in the Normal state.  If I preview the actual slide it is working fine, but when I publish or preview the whole project no Next button appears.  I have also tried this with a variable.  The variable changes correctly but I get the same result - no Next button

I have done this on many, many slides in the past but for some reason today they will not behave.  Any help is appreciated.  Small file with a sample attached.

Wendy Farmer

Hi Kay

see if it works how you want now.

I deleted the triggers to change the state of the buttons to visited as that is a default SL state and triggers are not required.

I added the trigger to change state of next button to normal 'when timeline starts' on the slide on condition both those buttons are visited.


Kay Fenton

Thanks Wendy for the quick response.

I added the extra trigger to see if that made any difference - normally I would not set a trigger for visited.  In my project file I have added the trigger for 'when timeline starts' but still have a couple of slides where it wont work.  When I copy and paste one of the problem slides into your project it works!!  My menu options are set to "free", so I am puzzled why it is sporadic. I do have some slides in the same project where the Next button is working fine without the timeline trigger, so its really stumping me!  I cant upload the whole file here - is there some way I can share it just with you?


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