SA Project- Use of Custom Theme (no5 and no6) without editing SA_Control-> Theme.ci

Hi Rune,
Bradley will likely be the best person to answer this question. But I think your best approach is to look at the code in Theme.ci and create your own Theme in your project.

Hi Rune,

To use theme 5 or 6 you need to do the following:

The workspace supports basic theming. By default we ship a number of themes out of the box such as Indigo, SEGreen, Black, Grey and in 2018 R2 “Blue”.

A theme consists of:

• Header bar Colour

• Control colour

The set of colours for the header bar are fixed. They are Black, Green, Grey, Orange, Indigo and Blue (2018 R2)

The set of colours for the control colours are also fixed. They are Green, Indigo, Orange and Blue (2018 R2)

A custom theme involves selecting a Headerbar colour and a Control colour.

1. In Citect Studio, navigate to Standards > Labels

2. Change the label “_THEME_Default” to 5 or 6.

a. We only support 2 custom themes.

3. Create a Startup function for your Clients with the following code:

a. Theme_SetHeaderColor(5, THEME_Header_Light)

b. Theme_SetHilightColor(5, THEME_Hilight_Blue)

4. [Save] the file

5. In your computers profile, ensure this function is called on startup of the client

6. Compile and Run up Citect

Thanks Bradley,


Would you please clarify following for my understanding:


If I use
Theme_SetHeaderColor(5, THEME_Header_Light)
Theme_SetHilightColor(5, THEME_Hilight_Blue) => Gives me compile error,

If I use
Theme_SetHeaderColor(5, THEME_Header_Light)
Theme_SetHilightColor(5, THEME_Hilight_Indigo) => Gives me orange buttons

If I use
Theme_SetHeaderColor(5, THEME_Header_Light)
Theme_SetHilightColor(5, 1) => Gives me my wanted Theme with Grey heading and Blue buttons


Thanks
Rune

Bradley,

If I use
Theme_SetHeaderColor(5, THEME_Header_Light)
Theme_SetHilightColor(5, THEME_Hilight_Orange) => Gives me blue buttons

Do you get the same?

Hi Rune,

No I didn't get the same... that's because I tested this on 2018 R2.... sorry about that.

1. THEME_Blue is new for 2018 R2. So that's why you get a compilation error
2. The colour mixup you are seeing is because we made an error in our theming indexes for Header and Control colour for 2018. They are swapped for Indigo and Orange. The Theme array "works" because they are swapped in that as well, compensating for the error. 2018 R2 already contains the fix to the labels, but we haven't rolled the change back to 2018.

Can you please lodge a support case to get this fixed.

bradley

2018 R2, is this version released?

I'll add this to the support case,

Thanks for clarifying

Rune

Not yet, not too far away. We're doing the final touches right now.

Beta program is still running if you want to check it out.

cheers,

bradley

@Bradley
It there a reason the Black and Grey theme use green for the buttons? It makes the combination of header bar and button colour not logical compared to the other theme’s like orange. This is the case on 2018 and 2018R2 beta

Hi Thijs-Jan,

The reason it is a "vibrant" colour is about awareness of what is selected in the operational areas of the UI (content, and zones). If for example we used a shade of grey for the light theme, then it would be very difficult to see what is selected (equipment, tabs options etc) at a glance.
So why Green? Well we were owned by SE, so we made a choice that Green will be the colour used on neutral themes such as Light and Dark. You can always change it, but your choices are Green, Orange, Indigo. And from 2018 R2 - Blue.

cheers,
bradley