Background colors for buttons

Waldemar.Hersacher · Mar 12th 2013

We are moving an applicaton programmed in C# from NetDCU8 and NetDCU11 to NetDCU14.

Some of our buttons have a background color. This works on the NetDCU8 and NetDCU11. But on the NetDCU14 the button is displayed in white and the text on the button is light grey.

This is the code from the designer:
this.CmdYes.BackColor = System.Drawing.Color.Green;
this.CmdYes.Font = new System.Drawing.Font("Tahoma", 9.75F, System.Drawing.FontStyle.Bold);
this.CmdYes.ForeColor = System.Drawing.Color.Lavender;
this.CmdYes.Location = new System.Drawing.Point(0, 14);
this.CmdYes.Name = "CmdYes";
this.CmdYes.Size = new System.Drawing.Size(48, 83);
this.CmdYes.TabIndex = 15;
this.CmdYes.Text = "JA";
this.CmdYes.Click += new System.EventHandler(this.CmdYes_Click);

Display Properties -> Appearance -> Scheme is set to Windows Standard.

Is there any visual styles setting I have to set?

hpb · Mar 12th 2013

Hello,
which kernel version do you use?

Waldemar.Hersacher · Mar 13th 2013

Currently I have either the beta version XIPV210_CE6Core_121217 fixing the CAN problem or the offical XIPV210_CE6Core_130122 installed.

I cannot check it here in the home office because I haven't the board.with me.

I have created a complete new standard application for .Net 2.0 with just a button in the dialog and made the background color green.

The light grey text is not a problem because we choose it for better contrast against(?) the green background.

The problem is just that the background color is missing. The background color of a label is working.

jopomo · Mar 26th 2013

Hello, this is a know issue for current kernels in NetDCU14.

0001524: [Display] Display failures with 2D HW Acceleration - new.

It's in the roadmap for solving in future kernels.

fs-support_ZU · Mar 26th 2013

Hello,
we will release a kernel (today), where you can adjust the HW acceleration settings by registry. The problem should disappear while use SW acceration only.

Code

reg open \drivers\display\lcd
reg set value AccelLevel dword 0
reg save
reboot

Waldemar.Hersacher · Mar 27th 2013

This didn't fix the problem:

[HKEY_LOCAL_MACHINE\Platform]
"KernelVersion"="NetDCU14 V1.04"
"KernelVersionDate"="Mar 25 2013"
"KernelVersionTime"="16:38:41"

[HKEY_LOCAL_MACHINE\Drivers\Display\LCD]
"VidMemBase"=dword:4f000000
"Mode"=dword:00000064
"AccelLevel"=dword:00000000

"AccelLevel" was 4 before.

The background color is not displayed on buttons.

jopomo · Apr 9th 2013

Hello,

exactly same problem for us, background button color is not working for VS2005 application with kernel v1.04

A new kernel v1.05 have been released yesterday that we have not tested yet, but in any case, the changelog does not indicate any changes to this issue.

Any idea ?

UPDATED: v1.05 does not solve the problem

fs-support_ZU · May 22nd 2013

Hello,
we investigate the â€žproblem with the buttons background colorâ€. Basically the variable SYSGEN_XPSKINâ€œ is responsible for this behavior. We can offer following solutions:

1.) Order a custom image "without" SYSGEN_XPSKIN.
2.) Set COLOR_BTNFACE in [HKEY_LOCAL_MACHINE\SYSTEM\GWE] to 0
3.) Set BtnOldSkin=1 in [HKEY_LOCAL_MACHINE\SYSTEM\GWE] -> needs image >= V1.06 (or BETA image, date = 132205 or later).

Waldemar.Hersacher · May 24th 2013

Hello,

I tested the solution 3.

I used the beta kernel XIPV210_CE6Core_130522_BETA and used

reg open \SYSTEM\GWE
reg set value BtnOldSkin dword 1

The user interface is now in the same old stile it was with NetDCU8 and NetDCU11 which dosn't matter for us. But more important the background color is back again.

jopomo · Jun 13th 2013

I can confirm that this option is now working in current kernel: XIPV210_CE6Core_130605 v1.06

But, if we like to mantein the new look of the buttons, which is the solution ?

fs-support_ZU · Jul 5th 2013

Hello,

Quote

But, if we like to mantein the new look of the buttons, which is the solution ?

So "3.)" would be the best solution, but in general XPSKIN and "button background color" adjustment is not possible anymore.

You may create your own button control deviated from a superior control class, but i dont know if this resolves the problem. An other possibilitie is to use bitmaps for the backgound.

Share