#Printing to HPLJ
9 messages in this thread
Hi Dennis,
Just a quick note. Just because it is not listed in the VB API reference
does not mean you cannot call the API.
Don Funk
There is 1 Reply.
Don,
Thanks for the hint! See my message to George Campbell. Funny thing,
though. The MS Windows Programmer's Reference lists the paramater as
GetSetPAPEROrient while Windows.H and the VB API reference call it
GetSetPRINTEROrient. Now I know why I couldn't find it in the VB API ref.
Do you know if this Escape parameter will be supported in 3.1?
–dennis
There are 2 Replies.
Hi Dennis,
I am glad you were able to get the Printer orientation solved. I have
gotten several people who have asked me how it can be done and have always
said that the Esacpe would do the trick, although I have never tried. Now I
have confirmation that it *can* be done within VB. I saw the code and saved
it and now I will create an article in the Knowledge Base for future
reference. Thanks a million for your efforts.
Don FUnk
There is 1 Reply.
Don,
re: Using Escape to change printer orientation
The only aspect of this that makes me a little uncomfortable is that the
GetSetPrinterOrient escape is only included in the API for backward
compatability and might not be supported in future win versions. You might
want to include this little disclaimer in any KB article.
There is 1 Reply.
Hi Dennis,
I would feel at ease about the use of this in future releases. If this
was not included, many older apps would be incompatible when ran under
future releases on Windows. I would look at a solution with ExtDeviceMode.
There is probably some advantage with it but have not had the experience
with it to give you the facts.
Don Funk
There is 1 Reply.
Don,
I'm sure the advantage with ExtDeviceMode is that you can set just about
all of a printers characteristics with just a single call unlike Escape
which can only change one characteristic per call. But until VB gives us
the ability to deal with driver exported functions, it'll require a .dll to
use ExtyDeviceMode.
–dennis
There is 1 Reply.
Hi Dennis,
I'm no expert on the API's but looking at ExtDeviceMode, I don't see any
problem with this API and using it in VB. It takes strictly data items with
no call-back function. Is there something I don't see such as an initializing
function that has to be called before you make this call? I see you have to
have an hDriver before, but you can get this from the GetModulehandle which
only requires a LPSTR of the driver name.
Don Funk
There is 1 Reply.
Don,
re: ExtDeviceMode
The problem isn't the paramaters but the procedure itself. Take a look at
the comments section for this call in the Programmer's Reference. This is
not a GDI function, but a function exported from the driver itself. Thus,
you need to do a GetProcAddress to get the entry point for the proc., and
use that address to call the proc. I don't think you can do this from VB.
Maybe I should just give it a try and see what happens.
–dennis
Hi Dennis,
I am glad you were able to get the Printer orientation solved. I have
gotten several people who have asked me how it can be done and have always
said that the Esacpe would do the trick, although I have never tried. Now I
have confirmation that it *can* be done within VB. I saw the code and saved
it and now I will create an article in the Knowledge Base for future
reference. Thanks a million for your efforts.
Don FUnk