I have a ListPicker on a page, and ListPickerMode=Full. Hit the “Win-Home” button to exit the app. Then hit the “back” button to resume the app. Boom! This is what I get.
The picker was not open or “active” at any point.
There’s not really much in my stacktrace. It’s triggered by “InitializeComponent()” when the page’s constructor is called. Anything before that is outside my code. I’m guessing the frame and content hasn’t been set yet, and it's hitting one of the issues where the app is resuming so fast that it's re-using the same process.
See attached screenshots
Comments:
The picker was not open or “active” at any point.
There’s not really much in my stacktrace. It’s triggered by “InitializeComponent()” when the page’s constructor is called. Anything before that is outside my code. I’m guessing the frame and content hasn’t been set yet, and it's hitting one of the issues where the app is resuming so fast that it's re-using the same process.
See attached screenshots
Comments:
ListPickerMode is read-only in the latest version of the toolkit (as of the November 2011 Toolkit).