When I set the navigation for an element on a screen to "Other... Go Back", it doesn't work. I navigate to the screen from a previous screen via "Go to another screen or URL" option. It seems that no matter what combination I try, I can't get the "go back" option to work for me. Is there a trick to getting this to work? It seems fairly straightforward so maybe I'm just missing something?
--- Thanks, Jeff
Hi, Jeff.
Don't know your specific situation, but the "GO BACK" option is a relative back. If you need an action to take the user back to a specific state/screen (i.e., absolute back), use the CHANGE THIS SCREEN > USE EXISTING STATE or NAVIGATE TO > PICK SCREEN option.
Elements with the "GO BACK" interaction will allow users to rewind their actions taken when using the prototype, as long as element is visible to the user. Does this information help?
I understand. I am attempting to use it as a relative action. However, it is not "going back" for me. It does nothing when I click on the element. The element shows up as highlighted so it knows there is an action there but it does nothing.
Thanks George! I noticed a difference but I'm not sure what's causing it. In your example, when I expand the screen interactions, only the first page is tagged as "Start" (at the top of the screen graphic in the screen interactions diagram) and all the other pages are displayed with navigation lines connecting them.
When I expand the screen interactions for any of my pages, they are all tagged as a "Start" page and there are no other pages depicted as being connected (as shown in your example). However, there are connections there because I can click on elements when running and display the appropriate page.
How does a page get tagged as the "Start" page and, more importantly, how can I remove the "Start" tag to get it working properly?
As I said, I was guessing your situation :D. Anyway, my interaction flow looks different coz I'm using page states. That said, I think I was able to recreate your situation. I redid the prototype that I shared with you earlier. That is, I now have a home, Screen A and Screen A1 as separate screens and not as states. On screen A and screen A1, I placed a back button to navigate back up the navigation hierarchy.
The back button is not taking me anywhere although it shows the golden highlight. Hold on till Monday so that someone from the Product dev team can take a look.
Great... Thanks! I'll look forward to the reply/resolution.
BTW, I forgot to answer your question about "Start". When you create a new screen, it's automatically the START state for that screen. When adding interactions, if you choose the "CHANGE THIS SCREEN" option, Indigo creates a new page state based on the START state, which you can tweak and animate. Indigo automatically names this state based on the action. For example, tapped/clicked ADD TO CART."
For more information, check out the following help topic explaining this concept in better detail.
The dev wizards have spoken, and it's a bug. It will be fixed in the next update, along with other goodies. Thanks for reporting it!
When the update is available, Indigo will inform you when it's available on launch. You can verify whether Indigo is set up to check for updates on launch; look under MENU > HELP & ABOUT > [x] automatically check for updates on startup.
-George
Hello,
This issue has now been resolved.
Please let me know if you have any questions.
Sincerely,ValerieDeveloper Support Engineer Infragisticswww.infragistics.com/support
Thanks for the info. I look forward to the next update!
Hello Jeff,
I have created a private case for you, CAS-109287-H7W0L7, in order to track this issue (development id 131571) and notify you when there are changes and the fix is available.
You can access this case at https://ko.infragistics.com/my-account/support-activity
Sincerely,
Valerie
Developer Support Engineer
Infragistics
www.infragistics.com/support