Summary: | Efficiently generate print data when Qt's new "arbitrary pages" feature is used | ||
---|---|---|---|
Product: | [Applications] okular | Reporter: | Michael Weghorn <m.weghorn> |
Component: | printing | Assignee: | Okular developers <okular-devel> |
Status: | REPORTED --- | ||
Severity: | wishlist | CC: | jeremy.lorelli.1337, m.weghorn, nate, oliver.sander, simonandric5 |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Other | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Attachments: | Patch that demonstrates the evaluation of pages to be printed (not meant for inclusion "as is") |
Description
Michael Weghorn
2018-01-19 14:13:35 UTC
Does the problem you describe vanish when you let Okular directly into a QPrinter (i.e., by printing with rasterization)? (In reply to Oliver Sander from comment #1) > Does the problem you describe vanish when you let Okular directly into a > QPrinter (i.e., by printing with rasterization)? No, the behaviour is the same, since Qt basically handles everything like it does for the "print all pages" ("QPrinter::AllPages" is set) and just passes the "page-ranges" option to CUPS, which then selects the relevant pages in the next step. *** Bug 421670 has been marked as a duplicate of this bug. *** |