psdrv: map Courier New to Courier
pilcher at concentric.net
Tue Feb 6 09:26:46 CST 2001
On Mon, 05 Feb 2001, you wrote:
> > Well, I couldn't get GetPrinterData to work. The driver would compile
> > OK,
> > but Wine was unable to load the driver, because it couldn't resolve the
> > 'GetPrinterData' symbol. (Probably something I did wrong.)
> You'd need to add the line
> import winspool.drv
> to wineps.spec
I *think* that I tried that. I'll doublecheck when I have a chance.
> Actually since you're storing the data as many values under a separate
> key would you mind moving the key to [..\Printers\<name>\FontSubTable]
> (i.e. get rid of the PrinterDriverData elememt), this will mean the
> GetPrinterDataEx will still be able to access the data (I really think
> that we should eventually use these APIs as hard coding the
> ..\Printers\<name> bit into the driver offends me ;) ).
What part offends you? I have not hardcoded the name of the printer
into the driver. It do my setup in PSDRV_GetPrinterInfo, so I have
the name available.
Does GetPrinterDataEx allow one to enumerate the values in a key?
Keep in mind that with this setup we don't know the value names.
Here is my initial patch. It doesn't include any of the changes you
suggest in your most recent note, but take a look and tell me what
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 7902 bytes
Desc: not available
Url : http://www.winehq.org/pipermail/wine-devel/attachments/20010206/dd589f41/wineps-reg.bin
More information about the wine-devel