https://bugs.kde.org/show_bug.cgi?id=440117
--- Comment #3 from Nate Graham <n...@kde.org> --- It's a matter of expectations and software architecture. macOS has a centralized print dialog that implements all of these kinds of options in it so that apps don't have to. In the KDE world, we use the Qt print dialog which does not implement all of these options. As a result, over the years apps have made their own homegrown implementations of these features which would conflict with a central implementation, were it to be created. If you want the Qt print dialog to be more like the feature-filled macOS print dialog, that would need to be done by the Qt folks, not us. As a part of this, they would need to come up with a process of handling conflicts between the dialog's implementation of features such as scaling vs the app's own implementation. It's a tricky thing. In my opinion, macOS got it right by investing in a feature-filled print dialog from the start, which limited the amount of work that 3rd-party developers had to do to add features that users expect. like scaling. -- You are receiving this mail because: You are watching all bug changes.
