Next and Back buttons

Feb 27, 2017

Hello Heroes,


I need some help please.


I created my own player, with "back" and "next" buttons. Then I disable the NEXT bt until the action it's over, and created an arrow that points to the NEXT bt when the action it's over. That arrow, is the trigger to change the state "disable" to "normal" on the NEXT bt. It works perfectly. BUT, if the user goes to the next slide, then e goes back, all the actions work fine, except the NEXT bt is disable, even after the arrow appears, and the arrow it's the trigger. Shouldn't this been working?

 


Here is the online project, and I attach here the AS360 project.

https://360.articulate.com/review/content/6a7c27f4-f2b4-4f1d-a75d-26bc7e333f0a/review

 

 Some questions:

- How can I solve this problem? I want to go back and be able to go NEXT again.

- How can I go back and the NEXT bt is already "normal", like "the user was here, so he don't have to wait do go next again"?

- And is it possible, me to go back, but to the end of the action (timeline), after all the animations over, and the NEXT bt is unlocked?


Really need some help, this go back and then the NEXT bt don't unlock as it should is killing me and my deadline.

 


Thanks in advance!

4 Replies
Wendy Farmer

Hi Fernando 

if you are using custom buttons on screen you should be able to set the 'revisit' option to resume saved state. See rough example. That answers Points 1 and 2. 

I don't think it's possible to return to timeline end when you revisit a slide. but someone else may chime in with a workaround

DIGIK Digital Knowledge

Hello Wendy,

Thanks for your help and the example, I have a question. I understand that you already have the "next" arrow in the screen, and it only stays "normal" (and visible) when you make the trigger by the other arrow.

My question is: where are you setting in the beginning, that the "next" arrow is not visible? In the states of that arrow, you only have "normal", on the timeline it appears at the beginning, but in fact, it only appears when the trigger is ON by the other arrow, how is this happening?

By the way: where do I set the "revisit" option? Maybe I know what that is, but by the way you told it, I'm not sure if it's the same thing.

About the 3rd point, I think it's already happening! When you go back from the 2nd to 1st slide, you have already the "next" arrow, and the other arrow on in the screen, so it's going to the next frame of that slide.

Really thanks for your help, and I want to understand better your solution.

As this was a major problem, I contact the support, they have also give me some answers:

"We added variables S1 to S4 t each slide respectively to identify if the slide has already been visited. This variable is set to True and will affect how the Next button becomes disabled as I also modified that trigger to execute if the value of these new variables are false. See the attached modified project."

I attached the project here, fell free to explore.

I'm making tests and thinking what's the best solution, so please give me some answers when you have time! Thanks again.

 

Wendy Farmer
Fernando Ferrão

My question is: where are you setting in the beginning, that the "next" arrow is not visible? In the states of that arrow, you only have "normal", on the timeline it appears at the beginning, but in fact, it only appears when the trigger is ON by the other arrow, how is this happening?

Hi Fernando 

in the states tab I have set the initial state to hidden

About the 3rd point, I think it's already happening! When you go back from the 2nd to 1st slide, you have already the "next" arrow, and the other arrow on in the screen, so it's going to the next frame of that slide.

And is it possible, me to go back, but to the end of the action (timeline), after all the animations over, and the NEXT bt is unlocked?

Sorry I misunderstood and thought you wanted it to return to the end of the slide which it doesn't do - it's at the beginning of the slide - but as long as your requirement is met.

Good luck with your project Fernando!

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