Right now there's some confusion about how the back button or cancelling scanning is handled and implemented in UWP.
At this point the UWP sample achieves this by changing some code in the sample itself. It would be nice to not have to do anything special for this in the app that is implementing the library.
PR #354 suggests using a new Frame (and keeping track of the previous frame to restore it when scanning is done). I like the idea of this approach but it needs some testing.
There's a number of other issues that are related to this, so I'm consolidating them into one new issue.
Right now there's some confusion about how the back button or cancelling scanning is handled and implemented in UWP.
At this point the UWP sample achieves this by changing some code in the sample itself. It would be nice to not have to do anything special for this in the app that is implementing the library.
PR #354 suggests using a new Frame (and keeping track of the previous frame to restore it when scanning is done). I like the idea of this approach but it needs some testing.
There's a number of other issues that are related to this, so I'm consolidating them into one new issue.