#160: Printing

[Lubomir I. Ivanov]

On 9 July 2013 19:02, Tomaz Canabrava <tcanabrava at kde.org> wrote:
>
>
> On Tue, Jul 9, 2013 at 12:53 PM, Lubomir I. Ivanov <neolit123 at gmail.com>
> wrote:
>>
>> On 9 July 2013 18:43, Tomaz Canabrava <tcanabrava at kde.org> wrote:
>> >
>> >
>> > On Tue, Jul 9, 2013 at 12:26 PM, Lubomir I. Ivanov <neolit123 at gmail.com>
>> > wrote:
>> >>
>> >> On 9 July 2013 18:19, Dirk Hohndel <dirk at hohndel.org> wrote:
>> >> > On Tue, 2013-07-09 at 12:02 -0300, Tomaz Canabrava wrote:
>> >> >
>> >> >>
>> >> >>         ok, i will keep you folks up to date on with the printing
>> >> >>         progress.
>> >> >>         as a side note (and AFAIK) it seems that Qt does not allow a
>> >> >>         custom
>> >> >>         tab in the print dialog. so what i'm doing right now is
>> >> >> create
>> >> >>         a
>> >> >>         custom print QDialog with all options that calls another
>> >> >>         dialog
>> >> >>         (QPrintDialog) with the hardware settings. found the
>> >> >>         suggestion at
>> >> >>         stackoverflow.com..
>> >> >>
>> >> >> Well, this is not "Qt" fault per se, it happens because of this:
>> >> >> "On Windows and Mac OS X, the native print dialog is used, which
>> >> >> means
>> >> >> that some QWidget and QDialog properties set on the dialog won't be
>> >> >> respected. The native print dialog on Mac OS X does not support
>> >> >> setting printer options, i.e. setOptions() and setOption() have no
>> >> >> effect."
>> >> >
>> >> > Hmm - that sucks. So maybe we need a dialog BEFORE the print dialog
>> >> > is
>> >> > called?
>> >> > How are other Qt programs deal with this?
>> >
>> >
>> > I'm a bit lost here because I never printed anything till today - but
>> > let's
>> > discuss this a bit:
>> > why a separate print dialog is needed before the OS one is called? is
>> > that
>> > because we need
>> > to do a 'page setup' before?
>> > if so, there's a QPageSetupDialog for that.
>> > http://qt-project.org/doc/qt-4.8/qpagesetupdialog.html
>> >
>>
>> we pretty much had this in GTK (see attachment).
>> so i drew the conclusion that a separate dialog is needed for the
>> application specific settings.
>>
>> QPageSetupDialog seems to be the standard (native) page setup that most OS
>> have?
>
>
> Yes, that.
>
> We can also disable the QPrintDialog and do our own dialog that setups the
> printer,
> I think this is what most ( not just Qt apps ) apps do on windows ( adobe
> apps are
> way different than corel, that are way different than firefox, etc.
> everything is a bit different
> and nobody uses the default printer anyhow. )
>
> A Easy way is to 'hijack' the QPrinterDialog for unix, fork it, and made it
> default for every other system.
>

i have no idea how to do that unfortunately, therefore i cannot help.
are you suggesting a custom QPrinterDialog with a second tab with the
Subsurface specific settings, similar to the one in GTK?
if so can you provide some (preferably detailed) guidelines how to achieve it...
also by forking wouldn't that cause any troubles...?

what i've started doing today is adding all the required sliders,
radio buttons etc in a QDialog class (i.e. separate dialog).

lubomir
--