On Event Creation > Add event. Window Interactions. First Tab "Link to". Why is there the option "Previous Screen" and not "Next Screen"???

mike shared this question 5 years ago
Answered

I would like to have a Button "NEXT" on my template. So I can avoid creating every link for the next page on every single page.

Comments (7)

photo
1

Hi Mike,


you have to look in "pagination action" instead of "link to". There you can add the event "first page", "previous page", "next page" or "last page".


I hope it helps you

photo
1

thanks for your answer Albert. I tried this already, but it does not work. I think this pagination is used for Pagination Datagrid (http://www.justinmind.com/prototyper/...) not for linking between Screens in the prototype

photo
1

If you want your 'Next' button (of your template) to go to another screen, you have to...


Option 1:


drag that button to the screen you want to link.


watch this tutorial: http://www.justinmind.com/prototyper/...


Option 2:


select that button -> click Add event -> on Click -> Link to -> keep the Internal Screen radio button selected (or External Address radio button if you want to go to an external web page like http://google.com) -> select the screen you want the button to link to -> then click OK

photo
1

thanks jon. I knew Option 1 and 2 already. I have to clarify that I don't want to create on every page a different link but have a single button on a template or master that links to the next screen. And even if I reorder the screens on the tree, the links are dynamically adapted. I would like to have a new feature "Next screen".

photo
1

Variables might help you. 'on Page Unload', you set the value of a variable, then on the next screen create 'on Page Load' event and add a condition.


Here's a tutorial on how to use variables: http://www.justinmind.com/prototyper/...

photo
1

Dear John. I'm trying to work with variables but it comes to the same strategy. You need to have a Link on the button set to the next page. And this has to be done manually for every button on every single Screen.


It does not solve my issue to have an Event that jumps to the next Screen on the same order of the "Scene Tree". Actually when ordering Screens on the Tree you are actually "programming" the screen order already.


I've seen that previous screen acts like a javascript command. history.back(). I've expected that it jumps to the previous Screen in my tree.


When I export the HTML-Prototype with the comments column the user can see the tree and navigate but it's far away from the content. That's the reason I wanted to have a NEXT button on the Screen. I understand it has to be done manually for every screen because Justinmind Prototypes does not support this basic functionality.

photo
1

Hi Mike,


It's a good idea and we will consider to add "next screen" function in a future update.