Pyqt print pdf

Sets the resolution of the print device to the screen resolution. This has the big advantage that the results obtained when painting on the printer will match more or less exactly the visible output on the screen. It is the easiest to use, as font metrics on the screen and on the printer are the same. This is the default value. This value is deprecated. It is equivalent to on Unix and on Windows and Mac.

Due to the difference between and , use of this value may lead to non-portable printer code. On Windows, sets the printer resolution to that defined for the printer in use. When rendering text on a QPrinter device, it is important to realize that the size of text, when specified in points, is independent of the resolution specified for the device itself.

Therefore, it may be useful to specify the font size in pixels when combining text with graphics to ensure that their relative sizes are what you expect.

This enum type is used by QPrinter to tell the application program how to print. This enum type is used to indicate whether QPrinter should print in color or not. This enum type specifies what paper source QPrinter is to use. QPrinter does not check that the paper source is available; it just uses this information to try and set the paper source.

Whether it will set the paper source depends on whether the printer has that particular source. The enum is used to describe the format QPrinter should use for printing. QPrinter will print output using a method defined by the platform it is running on. This mode is the default when printing directly to a printer. QPrinter will generate its output as a searchable PDF file. This mode is the default when printing to a file.

Note the difference between Point and. This enum is used to indicate whether printing will occur on one or both sides of each sheet of paper simplex or duplex printing. Both sides of each sheet of paper are used for printing. The paper is turned over its longest edge before the second side is printed. The paper is turned over its shortest edge before the second side is printed.

Aborts the current print run. Returns true if the print run was successfully aborted and printerState will return Aborted ; otherwise returns false. It is not always possible to abort a print job. For example, all the data has gone to the printer but the printer cannot or will not cancel the job when asked to.

Returns true if collation is turned on when multiple copies is selected. Returns false if it is turned off when multiple copies is selected.

When collating is turned off the printing of each individual page will be repeated the numCopies amount before the next page is started. With collating turned on all pages are printed before the next copy of those pages is started. Returns true if font embedding is enabled. Pages in a document are numbered according to the convention that the first page is page 1. If and toPage both return 0, this indicates that the whole document will be printed. See setFullPage for details and caveats.

Returns true if the printer currently selected is a valid printer in the system, or a pure PDF printer; otherwise returns false. To detect other failures check the output of begin or newPage. Returns the name of the output file. The default page order is FirstPageFirst. This is Manual or a printer tray or paper cassette. Returns the PDF version for this printer. The default is to return an empty string; meaning that QPrinter will try to be smart in a system-dependent way.

On X11 only, you can set it to something different to use a specific print program. On the other platforms, this returns an empty string. Returns the page range of the QPrinter.

After the print setup dialog has been opened, this function returns the value selected by the user. Returns the current state of the printer. Returns the current assumed resolution of the printer, as set by setResolution or by the printer driver. Sets the default value for collation checkbox when the print dialog appears. If collate is true, it will enable setCollateCopiesEnabled. Since each generation is an isolated job, it makes sense to use Qt's QRunner framework to handle the process -- this also makes it simple later to for example add customizable templates per job.

We're using the same approach seen in the Multithreading tutorial where we use a subclass of QRunner to hold our custom run code, and implement runner-specific signals on a separate subclass of QObject.

We need a QThreadPool to add run our custom runner on. Now we have the generator QRunner defined, we just need to implement the generate method to create the runner, pass it the data from our form fields and the start the generation running. We then construct a dictionary of data from our widgets, using the. We convert the numeric value to a string, since we are placing text.

To actually generate the PDF we create an instance of the Generator runner we just defined, passing in the dictionary of data. Finally, we take our Generator instance and pass it to our threadpool's. If you run the app now, pressing the button will trigger the generation of the PDF and the result will be saved as result.

So far we've only placed a single block of text on the page, so let's complete the generator to write all our fields in the correct place. Next we need to finish the text placement on the template.

The trick here is to work out what the per-line spacing is for your template depends on the font size etc. The y coordinates increase up the page so 0,0 is the bottom left so in our code before, we define the ystart for the top line and then subtract 28 for each line. For most of our form fields we can just output the text as-is, since there are no line breaks. If the text entered is too long, then it will overflow -- but if we wanted we can limit this on the fields themselves by setting a max length in characters, e.

For the comments field, things are a little more tricky. The field can be much longer, and lines need to be wrapped over multiple lines in the template.

The field also accepts line breaks by pressing Enter which cause problems when written out to the PDF. Which is nice. So unless someone else wants to tell me about approach 2 instead I think I'll shortly give this a go and see how it comes out! Yep, that was one of the posts I looked at the stackoverflow one, I mean. Which is fine by me! Though now I'm curious as to how you actually do that, as I said I haven't gone near painting?

Just my feeling though. If you are master at html you might produce cleaner html than my run at it :. For a very plain table, its not very complex but for varying cell widths and extra formatting, you suddenly have to have a small structure to keep that info and it slowly becomes big ger Also, you would have to keep a YPos for newPage handling and other small details. I certainly would not want to do any styling, bolding, drawing at all!

I thought the way the guy said that meant that you could somehow just tell QTableView to output to a QPrinter set to output PDF instead of to the screen, and it just handled all the drawing itself? HighResolution if not QPrintDialog printer, self.

HighResolution printer. PdfFormat printer. Improve this question. And watch the progress of printing? In the answer to your previous question I linked to this other answer that explains how to load and print html content. As I told you, just use setUrl. The answer about multiple printing is yes, but it can only be addressed in another question, as soon as you understand how to print pdf files. I'm sending pastebin with the code, if you could look at it pastebin. Show 10 more comments.

Active Oldest Votes. One possibility would be to use pdf2image which is A python 3. KeepAspectRatio, Qt. SmoothTransformation painter. Self-contained Sample Program I have slightly modified your code and created a completely self-contained example.

Accepted: with tempfile.