Another disabled button use question...

Sep 10, 2012

Ok so I have combed these forums, but can't seem to find quite the solution I need.

I have a menu with 4 buttons, each button links to a different scene, and at the end of each scene the learner is directed back to the menu.

I want the learner to start at lets say button 1 and proceed to 2 then 3 and so on...I have had no problems setting triggers and layers that direct the leaner they have proceeded out of order.

What i would like to do though is have buttons 2-4 disabled and not even clickable until the learner is directed back to the menu from the previous section.  I have been unable to figure out a solid way to how the buttons go back to normal one at a time as my learner progresses.  This seems to become even more tricky when using the states such as visited as a condition....going from disabled to normal counts as a condition and then consequently breaks any future condition that uses the visited state as a condition.

Any help would be appreciated, I have tried several different combinations of disabled, normal and triggers today to try and make my menu work as intended to no avail. 

I would think that having a disable function and also a enable function would help so that it was less dependant on states that are used in triggers.

Thanks in advance!!!

5 Replies
John Olha

Adrian,

Those are great for disabling a button after it has been visited which is not a problem for me, what I want to do is turn a button from disabled to normal once the previous button has been visited.  It is easy enough to do this for the first 2 of 4 buttons by having a new layer show, however being that the trigger is a visited state from the previous button the menu breaks.

I was able to get each button to turn from disabled to normal by adding a trigger on each previous button that sets the next button to normal, however that interaction only works if the menu slide is never left, once the user leaves the menu slide (to follow each scene) and then returns the slide no longer seems to remember that the previous button was actually clicked to release the next.

Confusing?  I have tried about 5 different methods to try and get this to work to no avail.  In a nut shell I only want a button to be active once the previous button and scene have been visited, of course I could work around this issue by just adding in an “oops” screen that directs the user to do the scenes in order, but this itself also has a few issues.

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