Thanks Matt for your clarifications.

We here, were under impression that this mechanism works like "last one wins" scheme, so you can finely tune the apperance at the control instance itself, when needed of course.

Considering "Application and then Control" situation, since the system does not *overwrite*, it remains several possibilities if you want to change something already set in the AppStyler:

1. Set "UseAppStyling" to False for the control instance and redo manually the whole styling using the "Properties" tab;

2. Write code in Initialize or Load event (for example) to overwrite those properties, set in Application Styler, you need to change;

3. Create a separate Style Library and and pass it to the control instance in the "StyleLibraryName" property. 

 Am I right on these assumptions?

Thanks

"Application Then Control" gives priority to the ISL file over the control-specific settings.  When resolving properties or appearances, the values are never *overwritten*; rather, only properties that haven't already been set are resolved.  This means that whenever using the "Application Then Control" resolution order, the Control will only resolve properties that the ISL didn't already have a setting for.

-Matt

You are right. I was not doing any special settings in code, however the setting was overwritten by the setting in the "isl" file, which was not properly set.

I have a question about the "Resolution order": when you guys say "Application Then Control" which one has the most priority?

Do you mean: <<set with the values in ISL and then overwrite with the values from the control's properties>>, or the other way arround?

-Octavian