QPrinter crash application
-
I think documentation is clear that you should not call setPaperSize
if that size is not supported by printer.
The result is undefined -
alex_malyu I am not able to understand what you mean. Could be clearer? You mean the problem is the printer that is causing the "Crash"?
-
@ alex_malyu I was referring at this "setPageSize":http://doc.qt.io/qt-5/qprinter.html#setPageSize using QPageSize
-
Hi alex_malyu,
If I using like this:
@QPrintPreviewDialog preview;
connect(&preview, SIGNAL(paintRequested(QPrinter*)), this, SLOT(request(QPrinter*)));
preview.exec();@"work", but don't show text in preview and if click in "Page Setup Button" application crash too:
!http://i57.tinypic.com/16jituf.png(crash qt printer)!
-
Hi Guilherme,
I'm having a similar, if not the same, problem.
As of Qt 5.4 there are a lot of functions, arguments, and enums with similar-sounding names. These two functions are obsolete:
@void QPrinter::setPageSize(PageSize newPageSize)
void QPrinter::setPaperSize(PaperSize newPaperSize)@The recommended function to use is:
@bool QPrinter::setPageSize(const QPageSize & pageSize)@
You could use it like this:
@printer.setPageSize(QPageSize(QPageSize::A4));@
I've been doing it that way and occasionally a customer will have a crash there. The common factor seems to be HP printers. What is your default printer on the computer that's crashing?
-
If you had to read the problem occurs in various situations
Eg.: if click in “Page Setup Button” application crash too.I can say that the problem was with the default printer that was problem in driver (actually the "COM"), deleted the door and the problem stopped. But the point is that it should have a system with "QObjectconnect" to detect the failure, since the windows the "QT" uses "createDC": @https://msdn.microsoft.com/en-us/library/windows/desktop/dd183490(v=vs.85).aspx@
So the problem is not with no deprecated method (see that in my second post I also used the correct method) but with the method "CreateDC".
Read this:
@
QWin32PrintEngine::initialize: CreateDC failed ()
QWin32PrintEngine::initialize: CreateDC failed ()@These errors appear before calling any method.
-
Just this afternoon I tracked down a similar printing problem that a customer was having. The problem originates in QWin32PrintEnginePrivate::initialize(), the same function that generates the warning message you're getting: "CreateDC failed."
The problem is that, for some printers, the PRINTER_INFO_2 structure that GetPrinter() returns can have a value of NULL for the pDevMode member. Elsewhere in Qt code it is assumed that pDevMode is not NULL and it is dereferenced causing a crash.
One of those places is QPrinter::setPageSize(). Another is QPageSetupDialog::exec(). These are two places where your program is crashing.
Here's a test program you can run (make sure the problem printer is the default printer). This test program uses that same win32 calls that Qt uses but doesn't use Qt for the printing. So you can use this to see if pDevMode is NULL. If it is, then I think my fix will work for both of us.
@// Win32PrintTest.h
#ifndef WIN32PRINTTEST_H
#define WIN32PRINTTEST_H#include <QString>
#include "Windows.h"// Run the print test <--- This is the function you should call
void win32PrintTest();// HELPER FUNCTIONS
// Converts a win32 printer status to a string (PRINTER_STATUS_*)
QString win32PrinterStatusToString(DWORD status);// Converts a win32 paper orientation to a string
QString win32OrientationToString(short orientation);// Converts a win32 paper size to string
QString win32PaperSizeToString(short paperSize);// Converts a win32 print quality to string
QString win32PrintQualityToString(short printQuality);// Converts a win32 duplex option to string
QString win32DuplexSettingToString(short duplex);// Converts a win32 default paper source to string
QString win32DefaultSourceToString(short source);#endif // WIN32PRINTTEST_H
@ -
Ok, "here is the header file":http://pastebin.com/57G1kgpF for the test code.
And "here is the implementation":http://pastebin.com/Cgh1U3tT
-
Hi,
Did you took a look at the "bug report system":http://bugreports.qt.io ? There might already be a bug about it and your input would be valuable.
-
Yes I should have checked before I created "this bug report.":https://bugreports.qt.io/browse/QTBUG-44349
Checking now it look's like there's a few old reports. Is it good etiquette to comment on those like "This is probably related and I think I have a fix."?
-
If you have a fix and would like to contribute it, just go ahead. Submit your patch to gerrit for code review and include the related bugs in the commit message
-
