Re: Windows Call (GDI)


[ Follow Ups ] [ Post Followup ] [ Signature.net Forum ] [ FAQ ]

Posted by Brian Levantine on Wed, 3 Sep 2003 09:57:03 :

Hi Robert. The original PtrDlg program did read the ptrbins for each
printer just as you describe. I removed that code from the current version
of PtrDlg but the original code can still be found in the DMW folder under
the name of PtrDg_Old.Ibs. Look for the word "bins" and you should find the
appropriate code. I know the code may be kind of cryptic due to the nature
of the API I'm using so if you can't figure it out let me know and I'll help
you out when I can find some time.

Brian Levantine
brian@signature.net


----- Original Message -----
From: "Robert"
To: "Multiple recipients of list support"
Sent: Friday, August 29, 2003 12:11 PM
Subject: Windows Call (GDI)


> Hi yall !
>
> We've been doing some research on the Windoze's Print drivers and found a
GDI call that allows us
> to pull the actual Bins from the printer driver.
>
> In all my search of the .h files I could not find the function # to call
from within Comet, nor do
> I know if the Win calls are filtered by Bryan's code.
>
> The function is DeviceCapabilities it uses the DevMode structure and the
Printer_Info_2 structure
> and the DC_ declaratives (DC_BINS is function 6).
>
>
> I also found a little piece of VB that scan all printer drivers and list
the Bins. It is
> confirmed, Win98 and WinXP uses different bin numbers for the Xerox N32
printer...
>
> If you'd like to see that little VB program just say so and I'll gladly
send the source to you
> (kind of short) and the 4 lines of instruction to make it.
>
> Have a Nice Day
>
> Robert
>
>
> __________________________________
> Do you Yahoo!?
> Yahoo! SiteBuilder - Free, easy-to-use web site design software
> http://sitebuilder.yahoo.com





Follow Ups: