[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    More about print problem in Qt-2.2.4 (possible Qt bug ??)
From:       Michael Goffioul <goffioul () imec ! be>
Date:       2001-03-14 8:47:42
[Download RAW message or body]

Hi,

I reported yesterday a print problem with QTextBrowser in qt-2.2.4. After investigating
it seems to be a Qt bug: when using "setFullPage(true)" with the printer object, Qt
produces corrupted postscript. A "/pageinit {" is missing in the PS data, resulting in
an unmatched closing brace, and then in an unreadable PS file.
The problem lies in "qpsprinter.cpp", and I guess the code has been changed in 2.2.4
so that PS generated is smart with tools like "psnup" (it was not the case with
2.2.3 and earlier). However, now I'm unable to view any PS generated by Qt if the
application uses "setFullPage(true)".

May I ask developers who use "setFullPage(true)" to test their application, and see if
the same problem occur (or if I'm the only one...) ? Just print to a file and view with
ghostscript.

I know that Qt-2.3.0 is out now, but KDE-2.1 relies on Qt-2.2.4, and if I'm right, then
users won't be able to print from KDE apps using "setFullPage(true)", which is IMHO
a severe problem. But I may be (I hope) wrong.
Note also that I don't know which apps use the offending statement, so I don't know
"how severe" the problem can be.

Thanks.
Michael.

--
------------------------------------------------------------------
Michael Goffioul                IMEC-DESICS-MIRA
e-mail: goffioul@imec.be        (Mixed-Signal and RF Applications)
Tel:    +32/16/28-8510          Kapeldreef, 75
Fax:    +32/16/28-1515          3001 HEVERLEE, BELGIUM
------------------------------------------------------------------



 
>> Visit http://master.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]