A client called me, because printing isn’t working well in 2016r4.
Code like this:
[code] dim g as Graphics = OpenPrinterDialog
if g <> nil then
g.ForeColor = &c000000
g.DrawLine 0, 0, 200, 200
g.DrawString "Hello World", 200, 100
end if[/code]
and print looks ugly in 2016r4, but fine in 2016r3.
Tim_Wolff
(Tim Wolff)
December 15, 2016, 11:25am
3
I have the same problem, is there a solution for this?
I can’t use r4.1 as long as this “ugly printing thing” exists…
Bob_Keeney
(Bob Keeney)
December 23, 2016, 12:18am
5
Honestly, I can’t recommend that people migrate to R4 with printing this messed up for Windows apps.
DaveS
(DaveS)
December 23, 2016, 4:43am
6
you could route the output to gPDF
should just be one or two lines of additional code,
just an idea
I found printing directly is crap, but printing to pdf then printing the pdf was fine. This was from a Xojo report. As my client is printing to pdf to email this hasn’t been a problem for them.
Did anyone experience problems with direct printing to Dymo labelprinter ?