Next Button

Hi Mohammed and welcome to the community!

You cannot hide and then show the Next button (or the player).  

Instead, you can assign a condition that tells the Next button to go to the next slide only if say a variable or state has been achieved.  Take a look at my file.  I've created a variable called AB and set it to False.  When the learner clicks the B button, they see the B layer which then switches AB variable to True.  The Next button will only go to the next slide if AB = True.

If you need more help let me know.

My version above uses a variable to track what the learner has done.  You can also use states (assigned to Button A and Button B) and have the conditions of the Next button refer to these instead of a variable.

Hi Mohammed and welcome to Heroes! 

It looks like Simon has you covered here, but I also wanted to point you a tutorial that explains a similar set up. 

Of course, situations like this are reasons why many of us like to do our own navigation buttons, even though they sometimes can be more work.  Greater flexibility and control.

Thank you so much MR Simon Perkins. Much appreciate it. I have learned "variables" from you. I will try and will let you know the result. Please bear with me as I am the slow learner.

Thank you very much Ashley Terwilliger and Gerry Wasiluk.

I would like to share the steps that how I did my set up to achieve my requirements:

Requirements:

"A" Click + "B" Click = "Next"

Steps:

1. Variables

Name: A

Type: Value

Value: False

(same for B)

2. Create New Triggers:

Action: Adjust Variable

Variable: A

Operator: Assignment

Value: Value   True

When: When Clicks

Object: A

(same for B)

3. Player Triggers

On Condition

A = = Equal to True

AND B ==Equal to True

-----------------------------------------

Now my requirement is: 

"A" Click + "B" Click = "Next"

or

"B" Click = "Next"

so if the learner click "A" they have to click "B" and then only the "Next" button functions.

however, if they click directly "B" and then "Next", the button should function.

For the above requirements, please kindly advice on the changes to made in steps, if you don't mind.

If not please ignore this.

Thank you very much.

Many Thanks to Simon Perkins! Now I understand and did it successfully..!!

Glad you got it working Mohammed.

Variables, triggers and conditions will become easier to use with a bit of experimentation.  They're logical - but that doesn't automatically make them simple.  Some (or a lot of in some cases) trial and error is often required, especially when you start creating complex demands.  But the beauty of all three is that you can build intelligent and dynamic scenarios/interactions/sequences that really make a difference to the learner.  After all, that's part of what we're here for is it not?

Hi Mohamed,

Thanks for the update and I'm glad you got everything working as you needed with Simon's help. I'd agree with Simon as well that experimentation is the best way to learn how variables, triggers and conditions work.