Hi byo,
Btw., did I say that wxSmith is great?
It really is.
In this case I was not really thinking of custom events (although that would be great). All I wanted was to tell wxSmith to to associate any toolbar events (standard or custom) with my wxMyToolBar class, so that the event handlers were generated there. Even if this is only for the standard events that are currently supported, it makes for a cleaner design. As it is now I tend to get too many event handlers in my frame class. If I want to have event handlers in wxMyToolBar, I must do it manually and not via wxSmith. So being able to say which class is to handle the event seems like a good idea to me.
I guess custom events might be useful too, but it isn't all clear to me exactly what it should be like or when it would be useful. Perhaps describing some good example would clarify it. One thing I have seen, is the need for some way to put other items in a toolbar. For example, it should be easy to place a combo box in a toolbar using wxSmith, and then handle events in the containing toolbar class.
But the initial idea was being able to direct standard events to my own class, and not just the wxFrame derivative. I hope you understand what I mean.