El 23/12/2010 02:32 p.m., Schmidt escribió:
> "Eduardo"<mm@mm.com> schrieb im Newsbeitrag
> news:ievvm3$s26$1@speranza.aioe.org...
>
> [PDF-Printing]
>> I'll have to modify the App, I will have to replace Printer
>> by PrinterObject and send it (the PrinterObject) as a
>> parameter to the procedures that performs the printing,
>> but I could do that in a few minutes if I had a class that
>> fully emulate the interface of the VB Printer object.
>
> What methods/properties of the VB.Printer-Object
> are you using currently?
> Are there 5, 10 15? In either case you would need
> to write your own Printer-Object-wrapping class
> to achieve your goal (since there's no such thing
> out there "ready to be thrown in" AFAIK).
>
> In case we're talking about 10 different methods
> and properties - it cannot really be *that* much more,
> since what you're using is perhaps ScaleMode, ScaleWidth,
> ScaleHeight, PaintPicture, Line, and TextOut (Print-)
> methods - then that seems like a task, which is doable
> (given the PDF-helper-class you're mapping to, is
> at least capable, to draw lines, images and has a TextOut-
> method).
>
> Not in a few minutes of course, but also not that
> long as you may think (a few days I'd say, including
> testing - and slight adaptions per Search/Replace in
> your Printer-DrawingCode, sinceVBs Line-Statement
> is a bit "out of line" with regards to adequate method-
> encapsulation in your new written wrapperClass).
>
> Olaf
Yes Olaf, I have to check, but yes, mat be 10 or so.
All Scale*, CurrentX/Y, Print, Line, Font*, ForeColor, NewPage, EndDoc,
Page...
Yes, I can modify that class that I found or wrap it into another class,
but I thought that probably someone else already did it and may be
available somewhere (it seems that it isn't).