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

Adding access to page buttons on PrintPreviewDialog by keyboard shortcut keys #3929

Conversation

SergeySmirnov-Akvelon
Copy link
Contributor

@SergeySmirnov-Akvelon SergeySmirnov-Akvelon commented Sep 16, 2020

Fixes #3682

Proposed changes

  • Adding support of keyboard shortcut keys for access to page buttons on PrintPreviewDialog

Customer Impact

  • The user will be able to switch between viewing modes using the shortcut keys (Ctrl+1, Ctrl+2, etc) on PrintPreviewDialog

Regression?

  • No

Risk

  • Minimal

Test methodology

  • Manual testing

Test environment(s)

  • Microsoft Windows [Version 10.0.19041.388]
  • NET Core 5.0.100-rc.1.20420.14
Microsoft Reviewers: Open in CodeFlow

@SergeySmirnov-Akvelon SergeySmirnov-Akvelon added the waiting-review This item is waiting on review by one or more members of team label Sep 16, 2020
@codecov
Copy link

codecov bot commented Sep 16, 2020

Codecov Report

Merging #3929 into master will decrease coverage by 31.15033%.
The diff coverage is 0.00000%.

@@                 Coverage Diff                  @@
##              master       #3929          +/-   ##
====================================================
- Coverage   67.59941%   36.44908%   -31.15034%     
====================================================
  Files           1415         933         -482     
  Lines         505784      250363      -255421     
  Branches       41079       36785        -4294     
====================================================
- Hits          341907       91255      -250652     
+ Misses        157924      153876        -4048     
+ Partials        5953        5232         -721     
Flag Coverage Δ
#Debug 36.44908% <0.00000%> (-31.15034%) ⬇️
#production 36.44908% <0.00000%> (+0.00697%) ⬆️
#test ?

Flags with carried forward coverage won't be shown. Click here to find out more.

</data>
<data name="sixpagesToolStripButton.Text">
<value xml:space="preserve">Six pages</value>
<value xml:space="preserve">Six pages (Ctrl+5)</value>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What was the reason to go with Ctrl+5 and not with Ctrl+6? Did you find any guidance about it?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This was my suggestion #3682 (comment) that everyone has agreed with.

In my opinion it is a logical sequence - option 1, 2, ...5, and not based on number of pages. E.g. if there was a sixth option to show 12 pages - as a user I wouldn't expect CTRL+12 but CTRL+6.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Had you guys looked at what Office or windows are doing in similar cases?

Copy link
Member

@RussKie RussKie left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

Winforms.sln Outdated Show resolved Hide resolved
@RussKie RussKie added 📭 waiting-author-feedback The team requires more information from the author and removed waiting-review This item is waiting on review by one or more members of team labels Sep 17, 2020
@ghost ghost removed the 📭 waiting-author-feedback The team requires more information from the author label Sep 17, 2020
RussKie
RussKie previously approved these changes Sep 17, 2020
@SergeySmirnov-Akvelon SergeySmirnov-Akvelon force-pushed the Issue-3682_Keyboard_shortcut_key_is_unavailable_to_access_the_buttons branch from a589c8f to 08a78c7 Compare September 17, 2020 08:55
Winforms.sln Outdated Show resolved Hide resolved
@ghost ghost added the 📭 waiting-author-feedback The team requires more information from the author label Sep 18, 2020
@ghost ghost removed the 📭 waiting-author-feedback The team requires more information from the author label Sep 18, 2020
@RussKie
Copy link
Member

RussKie commented Sep 25, 2020

/azp run

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@RussKie RussKie merged commit a0dbee8 into dotnet:master Sep 25, 2020
@RussKie RussKie deleted the Issue-3682_Keyboard_shortcut_key_is_unavailable_to_access_the_buttons branch September 25, 2020 05:48
@ghost ghost added this to the 6.0 Preview1 milestone Sep 25, 2020
@dotnet dotnet locked as resolved and limited conversation to collaborators Jan 30, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Accessibility] Keyboard shortcut key is unavailable to access the buttons(One Page, Two Page...)
3 participants