is it ok to override system provided navigation mechanism? RRS feed

  • Question

  • I am working on a metro style app that has groups and items. I want to provide two views (groups first, user can click on the group to go to items view)  since I could not provide grouped collection view - some limitation in the GridView implementation . Instead of having two separate XAML file for these two views, i'm having one page (MainPage) and manipulating CollectionViewSource.Source to changing the data source, so that same XAML file displays two views (Groups and Items).

    When navigation comes back to main page, i'll attach data source.

    Is it ok to do this way, any confusion since there is a built-in navigation?

    Also is there a way to debug loaded visual tree and understand memory constraints?

    Any help is appreciated.


    Wednesday, May 9, 2012 11:42 PM

All replies

  • I don't know what the confusion would be.

    Matt Small - Microsoft Escalation Engineer - Forum Moderator If my reply answers your question, please mark this post as answered.

    Thursday, May 10, 2012 7:35 PM