To whomever wrote and documented the Printers unit. You deserve a punch in the baby maker. ( I kid) ((mostly))

-
To whomever wrote and documented the Printers unit. You deserve a punch in the baby maker. ( I kid) ((mostly))

For everyone else you can not use it in multiple threads reliably.

That is all.

Comments

  1. Phillip WoonAugust 9, 2013 at 10:05 PM

    Not sure if this is applicable, but we used ReportBuilder in DLLS where multithread .Net apps would use interops to call into the dll and produce reports.  I made sure the DLL was thread safe.  It seemed to work

    ReplyDelete
  2. Iman CrawfordAugust 10, 2013 at 7:12 AM

    Since this was only one report, in one application we just duped the Printers unit. Not the best solution.

    ReplyDelete
  3. Warren PostmaAugust 11, 2013 at 8:02 PM

    It is a system singleton. Wrapping a global process level win32 API and its state. If that surprises you, you may also be surprised to learn that the VCL and RTL are merely Win32 API wrappers at some level. In the end it comes down to the win32 apis especially GDI for Ui and printing.

    ReplyDelete

Post a Comment