Hi Huw.
We have only filenames in the registry. The current code works fine with the adobe postscript driver and various other driver for PDF printers.
Which native driver makes problems?
Why do you add spaces before and after the the function args and change idention, bracket style and variable names everywhere in the patch?
HP is using a subdirectory for some driver files, but i can't remember the driver name at the moment.
On 16/05/2012 17:22, Detlef Riekenberg wrote:
We have only filenames in the registry. The current code works fine with the adobe postscript driver and various other driver for PDF printers.
No, the current code copies the entire contents of the DRIVER_INFO struct's filename entries - this isn't what Windows does. For example it clearly doesn't make sense the copy the entire path if APD_COPY_FROM_DIRECTORY is specified... I've written tests to confirm this, but they can't be added to the test suite, since we'd need a real driver file for this to succeed.
Huw.