Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Request] Add backwards and forwards navigation including using mouse buttons #2603

Open
rayburger opened this issue Sep 24, 2018 · 4 comments
Labels
feature The issue is a request for a new feature in the generated projects. A feature is different from a pa Investigation
Milestone

Comments

@rayburger
Copy link

It would be amazing if every app built with WTS automatically includes backwards and forwards navigation through the stack using the keyboard, mouse (side buttons) and even Xbox controller.

For an implementation see https://github.com/Microsoft/Windows-universal-samples/blob/master/Samples/XamlUIBasics/cs/AppUIBasics/Common/NavigationHelper.cs

@crutkas
Copy link
Member

crutkas commented Sep 24, 2018

interesting idea, want to help and build out a proof of concept what this would act / look like for a navigation view app?

@rayburger
Copy link
Author

Is a PoC necessary to build, or can the XAML Controls Gallery (aka XamlUiBasics) app from the Windows Universal Samples repository act as PoC? This already uses NavigationView and implements keyboard (alt-left and alt-right arrows) and mouse back and forwards (XButton1 and XButton2) in the navigation stack, plus backwards using the Xbox controller.

@crutkas
Copy link
Member

crutkas commented Sep 24, 2018

i do as i think proof of concepts help see how something would work in a system like template studio. some of those samples can over simplify an issue and want to see how something works before we go full scale implementation.

how does the nav system work in maybe when you have a page with a media player?

@mrlacey
Copy link
Collaborator

mrlacey commented Oct 1, 2018

The generated code should already include hardware button support for back navigation (as per #1770)
According to the notes on that issue Prism also support forward navigation via hardware buttons.

Some questions

  • Are there issues with the current generated code that mean the back button doesn't always work? Or not work with some hardware buttons?
  • What examples are there of apps that use forward navigation within an existing stack, rather than to a new page?
  • Is forward navigation something that every app needs?
  • Would forward navigation via hardware buttons be useful as an optional feature?

@mrlacey mrlacey added this to the Backlog milestone Nov 15, 2019
@sibille sibille added the feature The issue is a request for a new feature in the generated projects. A feature is different from a pa label Jun 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature The issue is a request for a new feature in the generated projects. A feature is different from a pa Investigation
Projects
None yet
Development

No branches or pull requests

4 participants