Summary: | Cannot set print margins to zero - renders Okular useless for printing labels | ||
---|---|---|---|
Product: | [Applications] okular | Reporter: | editor |
Component: | printing | Assignee: | Okular developers <okular-devel> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | editor, ludwig.schweitzer, nate, richard.llom, simonandric5, suse |
Priority: | NOR | ||
Version: | 1.0.0 | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | Typical screen grab (shows "down arrows" greyed-out |
Description
editor
2016-12-31 23:14:00 UTC
Created attachment 103120 [details]
Typical screen grab (shows "down arrows" greyed-out
The printing dialog is QPrintDialog from Qt libraries. Please report this issue directly to Qt developers via https://bugreports.qt.io/ Seems a bug was reported ages ago regarding missing functions on QT print dialog. However, setting a page to print full page is possible already, apparently... "This is already possible using the QPrinter::setFullPage(bool) function." (In reply to editor from comment #3) > Seems a bug was reported ages ago regarding missing functions on QT print > dialog. However, setting a page to print full page is possible already, > apparently... > > > "This is already possible using the QPrinter::setFullPage(bool) function." Would you mind sharing the link to the qt bugreport? > > "This is already possible using the QPrinter::setFullPage(bool) function." > > Would you mind sharing the link to the qt bugreport? https://bugreports.qt.io/browse/QTBUG-3546 And here is the documentation of that flag: https://doc.qt.io/qt-5/qprinter.html#setFullPage This isn't an issue with Okular or the Qt print dialog; the allowable minimum margins are determined further down the printing stack, by CUPS or LPR another part of the printing system. My printer + CUPS +LPR combination allows 0" margins on all sides, for example. You might try reporting against CUPS or LPR. *** Bug 388485 has been marked as a duplicate of this bug. *** |