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

WPF PrintDialog "Pages" option only allow input single page range, it should support multiple page ranges. #10595

Open
JaneChen8989 opened this issue Mar 18, 2025 · 2 comments

Comments

@JaneChen8989
Copy link

Description

WPF PrintDialog Pages option only allow input single page range, it should support multiple page ranges.
If users need to print page "2,5,6", as current WPF Print Dialog, users need to open the Print Dialog three times in order to print "2", "5" and "6".
To be efficient, the Print Dialog should support multiple page ranges.

Reproduction Steps

WPF PrintDialog supports UserPageRangeEnabled property.
PrintDialog printDialog = new PrintDialog();
printDialog.UserPageRangeEnabled = true;

If set this property to "true", the WPF print dialog will enable "Pages" option. If users select "Pages" option, users can input single range such as "2-4" or "5" into the input box.
However, if users input "2-4, 6, 8-9" in the input box and click the Print button. The warning dialog displays and tell users that it only allows single page range.
In order to print "2-4, 6, 8-9", users need to open the WPF print dialog three times in order to print "2-4", "6" and "8-9" separately.

Expected behavior

the WPF Print Dialog should support multiple page ranges such as "2-4, 6, 8-9" for "Pages" option.

Actual behavior

WPF PrintDialog supports UserPageRangeEnabled property.
PrintDialog printDialog = new PrintDialog();
printDialog.UserPageRangeEnabled = true;

if users input "2-4, 6, 8-9" in the input box and click the Print button. WPF application should print 2, 3,4, 6, 8 and 9 pages automatically and without complaint.

Regression?

No response

Known Workarounds

No response

Impact

No response

Configuration

No response

Other information

No response

@JaneChen8989
Copy link
Author

Image

@miloush
Copy link
Contributor

miloush commented Mar 18, 2025

Seems like a reasonable request, but it will need an API proposal.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants