Re: Printing to a file

2006-07-30 Thread Detlef Riekenberg
Duane Clark wrote: > Detlef Riekenberg wrote: > > > > My direction to fix printing in wine is from low-level to high-level. > > Print-Monitors are already managed in git-HEAD, and they are loaded and > > used in my tree (Port-Functions). > > Afterwards, the Printer-Functions will be updated and t

Re: Printing to a file

2006-07-17 Thread Duane Clark
Detlef Riekenberg wrote: My direction to fix printing in wine is from low-level to high-level. Print-Monitors are already managed in git-HEAD, and they are loaded and used in my tree (Port-Functions). Afterwards, the Printer-Functions will be updated and then "gdi.exe" (16-Bit) is no longer req

Re: Printing to a file

2006-07-17 Thread Detlef Riekenberg
Duane Clark wrote: > Currently, using the Wine supplied print dialog, printing to a file > results in a file named "FILE:". Yes, that's bug # 3975 > It looks to me like the correct place to do this is in gdi/printdrv.c > CreateSpoolFile(). Using dlls/gdi/printdr

Printing to a file

2006-07-16 Thread Duane Clark
Currently, using the Wine supplied print dialog, printing to a file results in a file named "FILE:". In Windows (at least Win2k) a simple one line dialog box is put up where the filename can be typed in. I don't see a reason why a full Save As dialog would not be preferable;