Bug 182794 - Options displayed on the print dialog don't "agree" with options under properties > advanced
Summary: Options displayed on the print dialog don't "agree" with options under proper...
Status: RESOLVED UPSTREAM
Alias: None
Product: kdelibs
Classification: Frameworks and Libraries
Component: print-dialog (show other bugs)
Version: unspecified
Platform: openSUSE Unspecified
: NOR normal
Target Milestone: ---
Assignee: KDEPrint Devel Mailinglist
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-01 22:10 UTC by Ivo Anjo
Modified: 2018-05-10 19:20 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ivo Anjo 2009-02-01 22:10:28 UTC
Version:            (using KDE 4.2.0)
Installed from:    SuSE RPMs

When I'm printing, for example in okular, I can set duplex printing in Options > Options. But I can also set it in Properties > Advanced.

The problem is, these two places refer to the same thing, but are not synchronized. So if I select "long side" on the options part of the dialog, the properties dialog will still have duplex printing off (the default option), which is, of course, very confusing.

Another possible solution is not to display the duplicated option on the advanced dialog at all.
Comment 1 Michael Weghorn 2018-01-16 16:16:27 UTC
While the original bug report is for KDE 4 (and thus Qt 4) and the "Advanced" tab has initially been removed from the Qt 5 print dialog, it is now back (in the current development branch). The bug mentioned here has been fixed there as well, see the following two changes:

https://codereview.qt-project.org/#/c/215131/
https://codereview.qt-project.org/#/c/215069
Comment 2 Michael Weghorn 2018-05-10 19:20:14 UTC
(In reply to Michael Weghorn from comment #1)
> While the original bug report is for KDE 4 (and thus Qt 4) and the
> "Advanced" tab has initially been removed from the Qt 5 print dialog, it is
> now back (in the current development branch). The bug mentioned here has
> been fixed there as well, see the following two changes:
> 
> https://codereview.qt-project.org/#/c/215131/
> https://codereview.qt-project.org/#/c/215069

Since this has been fixed in Qt, I'm closing this bug report now.