Prev: Simple hack to get $1500 to your home
Next: WinUSB large data question
From: jvilar on 1 Jul 2010 10:04
Solved, it seems a bug in the pscript driver: if there is any call to
IPrintCoreHelper[PS]::SetOptions() then ALL the font substitution table is
updated to the registry (if different than the default one). It seems that
the pscript maintains an internal "dirty" flag stating that there are changes
pending to save into the registry and that that flag is not properly set on
calling IPrintCoreHelper::SetFontSubstitution(), but calling SetOptions()...

"jvilar" wrote:

> Hi,
>
> I'm extending the oemps sample driver included in the sdk with a full ui
> replacement. When I try to modify the fonts substitution map by calling
> IPrintCoreHelper[PS]::SetFontSubstitution() method, the changes seem to be
> volatile and never reach the registry (I expected the table being persisted
> in PrinterDriverData\@TTFontSubTable as a multi string)
>
> Any clue?
>
> Thanks in advance
 | 
Pages: 1
Prev: Simple hack to get $1500 to your home
Next: WinUSB large data question