PlantScada - Startup/Timing issue for Theme_SetHilightColor when using custom theme

Thanks Jacky,

I've also found two workaround that seems to work. At least when using either of these in my start-up script I haven't been able to reproduce the issue. 

Alternative1:

 //Project Theme settings
Theme_SetHeaderColor(5, 0);
Theme_SetHilightColor(5, 1); 
SleepMS(0);
Theme_SetTheme(5);

Alternative2:

 //Project Theme settings
Theme_SetHeaderColor(5, 0);
Theme_SetHilightColor(5, 1); 

Theme_SetTheme(5);

Thanks Jacky,

I've also found two workaround that seems to work. At least when using either of these in my start-up script I haven't been able to reproduce the issue. 

Alternative1:

 //Project Theme settings
Theme_SetHeaderColor(5, 0);
Theme_SetHilightColor(5, 1); 
SleepMS(0);
Theme_SetTheme(5);

Alternative2:

 //Project Theme settings
Theme_SetHeaderColor(5, 0);
Theme_SetHilightColor(5, 1); 

Theme_SetTheme(5);

Gald to hear that you have found workarounds, Rune. In general, the internal start-up sequence should be compeleted before executing the user start-up code. Theme_SetTheme(_THEME_Default = 5) is actually called in the internal startup code. Maybe calling Theme_SetTheme(5) again after setting Header and Highlight colours in your startup code fixes the problem. Having a sleep is also good approach to ensure your code will be executed after completion of the internal start-up sequence.

Thanks again for you input and comments most appreciated. 

What is you opinion of using SleepMS(0)? There is a note in the help file, that "0" is not recommended even though we are allow to use it. In this startup I don't think using SleepMS(1) matter either. 

You are right that SleepMS(0) is recommended. In your case, SleepMS(500) should be good enough as end users wouldn't notice this time delay. 

Great, Thanks