Printing is not available preemptive. So it probably wouldn't be any faster ;)
An alternative would be to register a client at startup as a print machine? Regards, Wayne On Thu, 20 Sep 2018 at 09:23, Keisuke Miyako via 4D_Tech <[email protected]> wrote: > > pure speculation, but I will put it out there just in case: > > first, v15 is 32-bits and carbon, v17 is 64-bits and cocoa. > so there is a massive difference there. > > then, evidently the print option "Hide printing progress option" is no longer > supported in 64-bits, > http://doc.4d.com/4Dv17/4D/17/SET-PRINT-OPTION.301-3730865.en.html > which makes one wonder if interactive or progressive (from code perspective) > printing is not allowed by the system. > not sure if running in a background preemptive thread can make any difference. > > in general, printing on the server is not recommended, > which is why Microsoft intentionally ships the server edition of their OS > without printing features. > > back to Mac, would it work if you first produced PDF on disk and then send > that file to the printer (maybe using CLI/CUPS) in question? > > 2018/09/19 22:37、James Brown via 4D_Tech > <[email protected]<mailto:[email protected]>>のメール: > Has anyone had a similar experience? Any idea what could be causing this with > v17? > > > > ********************************************************************** > 4D Internet Users Group (4D iNUG) > Archive: http://lists.4d.com/archives.html > Options: https://lists.4d.com/mailman/options/4d_tech > Unsub: mailto:[email protected] > ********************************************************************** ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:[email protected] **********************************************************************
