I have two questions on driver behavior that I’m trying to figure out. In the new wingdi driver I have implemented text rendering using the GDI interface. The current implementation honors the height specified in chrht. I have measured the heights both on the screen and when printed via wingdi using the windows print function. The heights on the output device matches chrht; however, they appear smaller than the other device outputs (e.g. ps). Should I scale the fonts up?
When printing, the output matches the content on the screen exactly. If the background is black on the screen, it is black on the print version. When I compare to the ps driver, it appears the colored background is suppressed. Should I do the same when printing from the wingdi driver? Attached are two patch series for wingdi. The driver is still in an alpha state, so I don’t recommend applying to master or any branch that is important. There is still some issues with the multiple EOP that will require a keypress after a redraw event (e.g. resize, printing). Also, I have forced debugging, so there is a fair amount of output on the console. Most of the examples appear to render correctly. The driver does not support alpha blending or native gradient fills. I’m not sure if it is worthwhile to add these features in this driver, particular with a Direct2D version on the horizon. Also this version of the driver is non-unicode to make a lowest common denominator driver. I’m going to add unicode support because that appears to be the standard used by all the maintained/newer drivers. Any feedback is greatly appreciated.
0002-Implement-a-new-Windows-GDI-wingdi-driver.patch
Description: Binary data
0004-Revised-version-of-the-wingdi-driver-that-uses-Windo.patch
Description: Binary data
------------------------------------------------------------------------------
_______________________________________________ Plplot-devel mailing list Plplot-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/plplot-devel
