>Nick,
>
>I've highlighted the keyword in your reply
>
>>If the STOP button in the real world almost always is red, it just does not make sense for the clients.
>
>Since that word is in there programmers shouldn't have absolute control of a color. Let the user make their own choices to account for those ALMOST cases.

Except for the simple fact that there is no setting in the Windows Display properties for the Stop button broken out from all the other buttons *g*.

This is getting down to philosophy (as I read on another thread).

Users are users and they should be allowed to modify their desktop colors as they see fit. However, in the same breath, I have no problem saying that as a developer working for a client, I should be able to implement a color scheme designated by that client. If the choices fall within the confines of 'hindering functionality' (i.e. color blindness), I would, of course, counsel them to change. But if the choices fall within the realm of bad taste, it isn't my job or in my best interest to put up much of a fight.

So to top it all off, let's all agree to disagree. This isn't something that will cause the fall of civilization as we know it. Maybe we can all meet over a beer in New Orleans and bring it up again *s*.

And on a technical note (imagine bringing up something technical here *s*). VFP doesn't conform to the Windows Standards anyway with regard to color schemes. You actually have to chnage a default property. The default ColorSource for a Form is 3D Objects. If not changed by the developer, when a user changes the color for 3D Objects to change button color, the form changes as well. THIS IS BAD! Instead of 4 -3d Colors, it should be changed to 5 - Window Colors, IMHO.