If you want to use these commands, you'll have to tell the module it's ok to parse them by defining ecsIgnoreRc 0. This will tell ecs not to ignore the rc commands. It defaults to 1, meaning rc commands do not get parsed. So, before you think there is a major bug in the module, add this line before anything else.
Furthermore, there has been some speed inconveniences when recycling. Recycling doesn't always mean you want to re-apply the ecs settings to the system. Therefore, here's a hint for you: there are some text-modifying (like textedit.dll) modules out there to switch this parameter on and off dynamicly so you can script your own thing. Remember, this is litestep: you choose! E.g.: switch it on (ecsIgnoreRc 0) when changing themes and colors, switch it off (ecsIgnoreRc 1) when rebuilding the popup menu.
Example of use:
In contrast to the color related !bang commands, the rc commands expect regular hexed rc-color-formats. Enjoy that I also implemented the Microsoft stubs here (stub = other name, same function).
Example of use:
The following commands can be used to change nonclientmetrics from within your rc files. They expect a single numeric value.
Example of use:
Remember that font names always have to be quoted and that they may not exceed 32 chars in length (which is defined by Microsoft).
Example of use:
And then there are the values which only expect a boolean (so 0 or 1).
Example of use:
There is an rc command that stores your current system settings to an rc file (making theme-creation much easier).
Example of use:
There is an rc command to stop the deactivation of visual styles (XP or later). The default behaviour of ecs deactivates them.
Example of use: