While it is probably possible to use API calls to ask Windows XP what kind
of theme is active, what right do you have to override the user's choice
just so your program looks the way you think it should?
There may be valid reasons why a user does not want XP themes when working
in Access, e.g.:
- It makes scrollbars unusable and sections of the screen unselectable in
some places in Access.
- It makes it impossible to tell the difference between Null and False in a
triple-state check box.
- It blocks transparency of tab controls.
- It runs poorly on older hardware.
- It causes annoying flicker on some Access forms:
http://members.iinet.net.au/~allenbrowne/ser-46.html
Please consider whether it would be better to respect the user's choice than
to assume that you, as a developer, have the right to make those choices for
them.
--
Allen Browne - Microsoft MVP. Perth, Western Australia.
Tips for Access users -
http://allenbrowne.com/tips.html
Reply to group, rather than allenbrowne at mvps dot org.
"Deano" <ma**********@gmail.com> wrote in message
news:41***********************@ptn-nntp-reader03.plus.net...
Just noticed that if a user chooses classic mode in XP the display changes
to a Windows 2000 look. This messes up some aspects of how my forms look.
Is it possible to detect if the user has switched to this mode? I can
detect if the OS is XP but not if they have changed to this display mode.