17 Jul 2012 1:37 PM #1
Unanswered: navigationview back button failing on circular items
i'm pushing views onto a navigationview. some of these views link to other views. so we can up with a circular stack like
[a, b, c, b, etc...]
now, when i use the back button starting at say, the last item 'b' in the above array the back button will work until i get back to the first item 'b' and then the back button will stop working. no erros, nothing. just total, silent failure. i've also tried manually calling .push() on the nav view from this point, and that fails as well.
what about how I am doing this would cause the navigation view to be completely incapacitated like this?
19 Jul 2012 4:13 AM #2
- Join Date
- Mar 2007
- Gainesville, FL
- Vote Rating
What does the config look like for the b items? Do you use the id or itemId config? Are they the same instance or different instances of the same class?Mitchell Simoens @SenchaMitch
Sencha Inc, Senior Software Engineer
Check out my GitHub, lots of nice things for Ext JS 4 and Sencha Touch 2
Think my support is good? Get more personalized support via a support subscription. https://www.sencha.com/store/
Need more help with your app? Hire Sencha Services firstname.lastname@example.org
Want to learn Sencha Touch 2? Check out Sencha Touch in Action that is in print!
When posting code, please use BBCode's CODE tags.
19 Jul 2012 5:05 AM #3
the b items are instances of the same class.
have yet to find the underlying issue but have been able to determine that the nav view fails whenever i add a second instance of a class to the navigation stack and then return to the first instance. e.g. if it were
[a, c, b, c]
the back button will stop working when i return to c...but i can keep moving forward in the stack indefinitely with no issues. very strange.
what are some typical causes of nav view silent failure?
19 Jul 2012 7:26 AM #4
so i was able to fix this by removing the itemId config on classes c and b respectively.
I'm at a complete loss for why having an itemId would cause this problem and it'd be nice for future troubleshooters to have an understanding why. Silent component failures like this are massive time sucks
14 Aug 2012 11:34 AM #5
I also had this problem and resolved it by removing the itemId from the views that are added to the navigationview. This is a really nasty bug, I hope it gets documented and fixed.