Toolbox event codes

Is there a list for event codes in the toolbox.
At the moment I’m using a for loop to register event codes and then using a wimp_report_error to work it out.
For some I managed to get them (Menu click), but trawling through header files is painful!

Golly. Well if you come across any that are not mentioned in User Interface Toolbox, published by Acorn Computers Ltd, 1994, ISBN 1 85250 165 0, part of the C/C++ package, please let us know.

PWNED! (^_^)

You don’t need to know them. Just use your own instead of the default in ResEd. To see what codes are sent by default use ResTest. I find it easier to define your own events then you can give a button and a menu item the same event number and your code needn’t care what caused the event.

In addition, you will find details in the StrongHelp oslib manual, in the constants section for each of the toolbox objects.

@Gavin – Ah that will be the massive pdf that is near enough unusable on RISC OS, I wonder why I didn’t look in there ;-)

But seriously, I suppose converting it to html and making it searchable online is difficult due to copyright implications?
I’m not being sarcastic there (unusal for me, yes)
It’s a serious question, as I’m thinking of doing it.
If there are copyright implications, I’ll just make it not avaliable online.

The stronghelp is often really useful, really helped me out with the structures, but for the event_codes it just shows its an int and that’s it…

I ended up with a for loop and then trapping all the event codes from 1 to 9999 and working it out from there.

Defining custom events is OK for static icons and I’m doing that, but my programs will have dynamically created icons.
Some of them may have hundreds of icons, in theory thousands. Not sure riscos can handle that, I’ll have to see if it does or not – but that’s a way off and even if it can I’m not sure it’s a good idea. It sure doesn’t sound like one.

There is no difference between custom events and default events other than the value. So creating the icons dynamically or statically has no bearing in the decision whether or not to use them. Custom events are the best reason to use the toolbox.

@Colin: It’s specifically keeping track hundreds of different events, why I didn’t use them for dynamically created icons in my case – there didn’t seem much point, using the default event seemed to make more sense.
But I agree the custom events are fantastic.