Something is not clear in my mind. Well, I'll try to explain (stop me if I'm wrong at any step) :
For every UI resource, wxSmith manages a wxs file and its appropriated class in a h/cpp pair files. Everytime you modify the resource using the C::B/wxSmith's UI editor, some parts of these files are candidates to be regenerated. These parts are materialized in block starting with "//(*" and ending with "//*)". So, you have to take care to never add any code manually into these block to avoid any loss at next wxSmith regeneration.
But, outside of these blocks, is it safe to add any code manually ? Or does wxSmith be suceptible to overwrite/erase them at any moment ?
Elsewhere in the forum, about wxFormBuilder, I've read that we need to derive any wxFB generated class, because wxFB can entirely overwrite its h/cpp pairs without any warning. Is it different for wxSmith ?
Seeing wxSmith is able to generate event handlers, I assume that any code we can add manually in the body of these handlers are safe (ie. will never be erased or overwritten ; otherwise it would be a real problem). But what about any function helpers or manually added methods and properties ?
Well, knowing I like to keep project as simple as possible (and number of source files does matter), I would like to be sure of the utility to systematically derive any wxSmith class... Or I'll work directly in the wxSmith generated ones.
Could you make the point with me on this specific subject ? To derive or not to derive, that is the question
