Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 09 JUL 2002 05:30:23AM Colin Rule wrote:

We use PRINTER.DLL, but this is a 16 bit version, and of course fails from the 32 bit calls.

Is there a 32 bit DLL available.


At 09 JUL 2002 08:36AM Donald Bakke wrote:

Colin,

We use PRINTER.DLL, but this is a 16 bit version, and of course fails from the 32 bit calls. Is there a 32 bit DLL available.

I'm not speaking on Revelation's behalf, but I'm pretty certain I can predict the response. Given that the Printer.DLL and OIPI are virtually redundant methods, with the OIPI being the far superior product, I seriously doubt they will convert this. I could be wrong of course.

Do you have a lot of code using the Printer.DLL? Is that why you want to maintain it?

dbakke@srpcs.com

SRP Computer Solutions, Inc.


At 09 JUL 2002 10:36AM Colin Rule wrote:

I dont have much code, only 4 DLL calls.

I use it to calculate text height and width, without having to open the OIPI.

I can't recall exactly why, as it has been there for a long time, but I think it was added so I could calculate things without a blank page being wasted each time, eg for calculations of printer placements and export which does not use the OIPI.

It is probably the case that I could call the OIPI and not waste a tree every time I do, so I will have to investigate further.

Colin


At 09 JUL 2002 11:03AM Colin Rule wrote:

Have now checked the code and converted to OIPI calls instead.

It seems the PrintSetup=3 allows this to be hidden.

Thanks


At 09 JUL 2002 12:00PM Mike Ruane wrote:

Colin-

The Printer.dll was converted to 32-bit, and we still use it. I just tested it again

OIPI is a better tool, by a far piece.

Mike

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/8b999440e79db1b385256bf1003438ba.txt
  • Last modified: 2023/12/28 07:40
  • by 127.0.0.1