>>>1. Something in our mis applications startup turns the _screen.themes to .F. Code reference did
>>>not find any explicit _screen.themes. Do you know what might set _screen.themes to .F. other
>>>than the code assignment?
>>
>>SYS(2700) is the only thing I can think of that would do this.
>
>I found a _screen.themes = .F. somewhere in our code using debugger - and then found that code reference had it too...
>
>>
>>>2. From the help file I did not understand that _screen.themes setting overwrites everythig below. The
>>>way it is, you can only have themes as default for everything, and classical style for specified objects,
>>>but not classical as default and themes for specified objects. I think I'd like it both ways.
>>
>>I disagree. If you want this, set Themes to .F. in your baseclasses, and then set them on for selected classes. If you turn Theme support off at the screen level, how are you supposed to turn it on later?
>
>That's exactly what I did: themes=.f. in form class, and the checkbox value .f., and all is well now - thanks for assistance.
>
>I still think that if you can say "disable themes for this form when they are enabled for screen", you should be able to say "enable themes for this form when they are disabled for screen". In other words, when I set a property of an object that should not depend of a property of another object. If you put code in a method, that code is executed regardless of what happens elsewhere.

Doru,

IMO, this is strictly a user option. I've got an application that runs under XP both with and without themes. Fox determines whether or not themes are enabled, and draws the objects appropriately. For example, I've got an app that has both the form and _Screen setting for themes equal to true. Under XP, if themes aren't enabled, you don't get them. If they are, you do.