I just have a button on the left side and a StatefulNavigationContainer on the right side. After putting all together and overriding OnInitialize and ... putting Debug.Print-statements inside just to have some list, how my app is working, I found, that every click on the same button fires all that stuff, which may include complex de/rehydrating, maybe nested, also if there is no change of the content of the StatefulNavigationContainer, because the correct view is there, and some silly user (called Gerhard) just clicking the button for no reason (like a monkey).
With best regards
-----Ursprüngliche Nachricht----- Von: nro...@googlegroups.com [mailto:nro...@googlegroups.com] Im Auftrag von Rishi Oberoi Gesendet: Donnerstag, 10. Februar 2011 14:14 An: nRoute Betreff: [nRoute] Re: REQUEST: Little performance enhancement of containers
I don't think that's true as none of navigation containers re-use an instance of a view - they are always regenerated. Rishi
On Feb 10, 2:20 pm, "Gerhard Kreuzer" <gerhard.kreu...@liftoff.at> wrote: > Hi, > > Rishi, I finally found out, that if the user clicks a navigation link, but > the associated view is still present, the whole stuff (New, OnInitialize > ...) is fired, but for nothing, because the view is up to date and was never > destroyed. > > Maybe you can build in some check to prevent this actions, because complex > views with sub views holding sub containers making heavily use of the > de/re-hydration can couse lot of system burden just for nothing. > > Thanks a lot. > > With best regards > > Gerhard > > _____