@Wayne, this is about the only thing I could find on adding event handlers to wxFormBuilder:
--- begin quote from stack exchange[1] ---
Yes, apparently it is the way to only declare the new event handler in
the derived class (the one that wxFormBuilder creates when you do
Tools->Generate Inherited Class), and connect/disconnect it to whatever
control you want it to be linked to in the respective
constructor/destructor.
--- end quote ---
I think the primary reason for the superclass/subclass split is to have one file wxFormBuilder can auto-regenerate, and one file that is only generated once (and can after that be edited by the coder). From that perspective, I think the attached patch is correct.
Hmmm... let's try that again:
@Wayne, this is about the only thing I could find on adding event handlers to wxFormBuilder:
--- begin quote from stack exchange[1] --- destructor.
Yes, apparently it is the way to only declare the new event handler in
the derived class (the one that wxFormBuilder creates when you do
Tools->Generate Inherited Class), and connect/disconnect it to whatever
control you want it to be linked to in the respective
constructor/
--- end quote ---
I think the primary reason for the superclass/subclass split is to have one file wxFormBuilder can auto-regenerate, and one file that is only generated once (and can after that be edited by the coder). From that perspective, I think the attached patch is correct.
[1] https:/ /stackoverflow. com/questions/ 8255753/ how-to- add-personal- code-into- wxformbuilder- generated- class