It's discussed, though not in enormous detail, in the xrc overview. Unfortunately the 'derived dialog' section of the 'xrc' sample (one of the ones that comes with the wx source) doesn't actually use it. Perhaps none of its features require RTTI; in that case you don't need to do anything different at XRC level, just LoadDialog() using a wxNoBorderDialog pointer.Well to be honest I never tried. I chose the way as described above because I found an explanation in the wxwidgets forum / WiKi that time I needed it. As it was/is working I never touched it since. Maybe I'll try sub-classing. But this project has no high priority for me - its just a private tool that shall work and not be perfect.DavidGH wrote:Out of interest, did you try the 'subclass' method? I've always found it sufficient for my dialogs, and wxCrafter does import it without difficulty.
Getting a little off-topic now, but where can I read about sub-classing in XRC files? Is this do-able in wxCrafter? (I think so - if you mean the custom controls, right?) I am trying to get the wording right... what is what...?!
To subclass with wxCrafter, just fill in the derived classname in the 'Subclass' > 'Class Name' field of the Properties section.