2
jonathanpoulin
If I recall correctly, you have to fulfill the following conditions to see custom icons for custom commands in the TC menus:
- use 'wciconex.inc' file to declare your custom commands and get them enumerated there in a special order.
- use 'wciconex.dll' file to store your custom icons.
Then wciconex.inc might look something like this (to begin with):
Code: Select all
// * user commands mappings
10000=128 // em_FooBar1
10001=233 // em_FooBar2
where:
10000 is the starting number for your first user command (em_FooBar1) that is used in TC menu
10001 is the second number for your second user command (em_FooBar2) that is used in TC menu
...
10098 ... em_FooBar99 ...
The numbering there should follow the order as your customs commands go in the TC menus (not the order as they met in the usercmd.ini), i.e. the first custom command met in the TC menu should be listed as 10000, the second one as 10001, ... the 99 one as 10098, etc.
Once you decide to reorder your custom commands in the menu(s), you will need to reorder/renumber them in the wciconex.inc respectively.
10000=233 -ish syntax principle (10000-sh number, equal sign, other number) is a mandatory, everything other in the example there (behind //) are the comments, where:
10000=128 means em_FooBar1 will use 128th icon from wciconex.dll
10001=233 means em_FooBar2 will use 233d icon from wciconex.dll
It is expected that you create, and maintain your wciconex.dll icon library on your own.
A common recommendation is to take vanilla WCMICON*.DLL, rename it as wciconex.dll, and then add your custom icons there one by one as needed.
Sounds awful, but that's how it works as far as I know.
Still, once you develop your consistent approach, it will be pretty easy to maintain.
PS I would be glad if something has been changed in that regard and someone else would share some innovative hints and know-hows here.