Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Discussion: Selector control #6086

Closed
ghost opened this issue Oct 12, 2021 · 0 comments
Closed

Discussion: Selector control #6086

ghost opened this issue Oct 12, 2021 · 0 comments
Labels
area-SelectionModel discussion General discussion feature proposal New feature proposal team-Controls Issue for the Controls team

Comments

@ghost
Copy link

ghost commented Oct 12, 2021

image

The item selector is a common scenario, used by many controls such as NavigationView, Pivot, ListView, ComboBox and so on.
Currently, the selector is implemented individually for each control, and a lot of times there are differences in behavior.

My idea was to have a new selector control, which would be used instead by all of those, and could also be used in custom controls.
It would also be useful to allow having a selector style in TabView (as described in #5223). Multiple selection styles for a single control are also discussed in #2310.

Some animations that could be supported:

  • moving between two elements (NavigationView)
  • fading in/out (ListView)
  • animation when being pressed (ListView)
  • changing between two colors: two elements have different colored selectors (NavigationView used to have this), changing state.

The Windows 11 tasbkar supports multiple states: normal, selected, progress bar etc. There can also be multiple selectors visible at the same time.

Pivot currently has the selector span the width of the item, while the other selectors have it as a fixed size. This could be a property of the selector.

@ghost ghost added discussion General discussion needs-triage Issue needs to be triaged by the area owners labels Oct 12, 2021
@StephenLPeters StephenLPeters added area-SelectionModel team-Controls Issue for the Controls team labels Oct 20, 2021
@StephenLPeters StephenLPeters added feature proposal New feature proposal and removed needs-triage Issue needs to be triaged by the area owners labels Oct 21, 2021
@microsoft microsoft locked and limited conversation to collaborators Jul 22, 2022
@ranjeshj ranjeshj converted this issue into discussion #7442 Jul 22, 2022

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
area-SelectionModel discussion General discussion feature proposal New feature proposal team-Controls Issue for the Controls team
Projects
None yet
Development

No branches or pull requests

2 participants