Visited State For a Branching Page.
Jul 27, 2012
Hi I created a branching screen , in my branching screen there are 2 topic each topic contain 5 pages and i give three states for my button, not attempted, progress and visited.
i just need to give visited state for my button after visiting all 5 pages in the topic but once just clicking the button only am getting visited state, i already give a trigger for controlling visited state i created 5 variables and made it as false, in each page i visit i make it as true, and i give a condition in topic page.if my all five variables are equal to true then change button status to visited.this function will work but default button is giving visited state once am clicking only.
I got a solution for this , i called other trigger and made the button to show only visited state once all my 5 pages are visited. this is the simple function i wrote it.
"if any of my 5 variable are equal to flase then change button state to normal."
am just sharing my ideas, if you feel that i can fix this issue in more simple way then please free feel to right and share .
10 Replies
Thanks for sharing your ideas, Sinchu. Not sure if this is exactly the same functionality you're looking for, but it's cool nonetheless
The visited state is not really controlable would be better to use a custom state such a s completed see this file
Thanks peter, that link works fine but less detailing , its just a simple step to track the visited pages, and each button contain only one page, there will be a problem if pages are more than two.. any way thanks for your help.
Thanks robert....i am looking into the files, thanks
HI Peter please look this file...i have just created a simple tracking pages .its working perfect.
Nicely done, Sinchu Works great! Thanks for sharing.
u r welcome peter.
Thank you, Sinchu. Your file just showed me what I was doing wrong and why my tracker wasn't working. You WIN!
Thanks patricia
Sinchu,
Thanks again for your solution.
Walter
This discussion is closed. You can start a new discussion or contact Articulate Support.