A group row font appearance is discarded during printing

Hi Johann,

Thank you for providing us with a sample project. We have reproduced the issue and our developers are investigating it.

For now, you can set the OptionsPrint.UsePrintStyles property to True and configure the Grid printing appearance explicitly using the Print Appearances page in the Grid designer. I have updated your sample project to illustrate how to accomplish this.

Thank you,
Pavel.

Hi Pavel,

thanks for the Workaround. But I need the Fond customizable, so this workaround isn't that usable to me.
I havn't been working on that module for a while and just found out, that an equal bug exists since 10.1.6, and that is the "productive" library I use. Will it be fixed there, too? Will there be a new 10.1.x-Release or will I have to use the 11.1.x Version?

Thank you.

Hi,

I now fix it programmatic:
            gridView1.OptionsPrint.UsePrintStyles = true;
            gridView1.AppearancePrint.GroupRow.Font = ...
            gridView1.AppearancePrint.HeaderPanel.Font =...
            gridView1.AppearancePrint.Row.Font = ...
I had already tried this before, but didn't know I have to set
gridView1.OptionsPrint.UsePrintStyles = true;
Now it works fine.

Thank you.

Hi Johann,

First of all, I must say that the fix will be introduced for the 11.1 version only, because this fix changes the control behavior during printing, which may affect existing applications of our customers.

However, if you are using DevExpress v10.1.6, I believe that you can still use the workaround, because you can customize font settings used for printing via code:

	
[C#]
// Setting the font for printing
gridView1.OptionsPrint.UsePrintStyles = true;
gridView1.AppearancePrint.GroupRow.Font = new Font(font.Name, font.Size, font.Style);
gridView1.AppearancePrint.HeaderPanel.Font = new Font(font.Name, font.Size - 1, font.Style);
gridView1.AppearancePrint.Row.Font = new Font(font.Name, font.Size - 1, font.Style);

I have updated your sample project to illustrate the idea. Please let us know if this solution satisfies your requirements.

Thank you,
Pavel.

Hi Pavel,

like I wrote this workaround now works fine to me.
Thanks for your help and the answer, which Version contains the fix.