Ok, consider this a small rant...

I appreciate that many users like the way syscolor.dll changes their system colours, but personally I don't. So what? Well, whenever I check out a theme I usually go through $themedir$step.rc to comment stuff I don't want and change tiny things... But sometimes I miss the line that loads syscolor, and then my colours are "screwed up".

Now, it's no problem changing back, and I've got SysColorNoChange (or whatever the setting is called) but as some themes use older versions this setting doesn't always work.

Suggestion (should be easily accomplished): I'd be very happy if themers would add a line in their readme (or at the top of $themedir$step.rc) "warning" the user that the theme loads syscolor.dll! (I consider this a better thing, than prompting on first load, or not load by default, as I suppose many actually likes their colours changed to fit the theme ;) )

I've got nothing against the module by itself, as it is, but I don't need my colours changed. That's it.

the latest version of syscolor has this setting:

SCNoChanges true

if you put this into your personal.rc you should at least be safe from themes that use the latest version.

i appreciate the rant (i know what you mean), but it's not a big deal to comment it out, or if you miss it, just fix it with 3dcc.