Ok, lets clear things up, i think you have some confusion going on here....
I do. But I think I got rid of it when I deleted the lines from the .cpp and .h
No, all editor related things are stored in a xml file, that is only edited by the wxSmith plugin (the drawing thing in codeblocks you use to create the dialog)
the two .save files for main.cpp and main.h.
They are not used by codeblocks normally, only used if something went wrong. So do yourself a favor and DO NOT EDIT OR DELETE them...
closed CB and opened it back up. So far, that code's staying away. Fingers crossed here!
Ok, i thought that wxSmith loads it automatically. You will see as soon as you open wxSmith, edit something and save it will come back...
I absolutely do not understand where the problem is to remove the event handler within the wxSmith editor. Why people always have to workaround to problems that are not there. Use buggy solutions and think it will work.
Say, I'm using the wxTreebook. It works good for putting a lot on one form. But is there anything like a stacked widget for CB? It's abt the same as the wxTreebook...just doesn't have the tree.
Ok, now you talk about complete different?
But is there anything like a stacked widget for CB
codeblocks does not have anything of this... WxWidgets has it and wxSmith (a codeblocks plugin) probably has to support it.
I do not know what a stacked widget is. WxWidgets supports mostly only native window elements. So if your operating system supports it wxWidgets will have it. One possibility to share window elements across multiple pages is a notebook control. Yes wxSmith supports it. You can add new pages with a right click in the editor.
We do not support wxWidgets questions here... But if you have some problems creating some constellation of windows with wxSmith you can ask here...