Auto generated code should not be edited by hand.
//(*
// auto generated code, should not be edited
//*)
// here you can add custom code
Anyway using a splash screen for a border-less window isn't a good idea.You only need to change the wxFrame style according to your needs.
Auto generated code should not be edited by hand.
Thanks renega_666, but I didn't change anything in the autogenerated block as you can see below :
/(*Headers(TestFrame)
#include <wx/sizer.h>
#include <wx/textctrl.h>
#include <wx/panel.h>
#include <wx/frame.h>
//*)
#include <wx/splash.h>
class TestFrame: public wxSplashScreen
So, knowing TestFrame class is based on wxSplashScreen and seeing frame.h is well provided, wxSmith/CB shouldn't regenerate reference to "frame.h" anymore. So, is there a difference of behavior between wxSmith and wxFormBuilder ?
Anyway using a splash screen for a border-less window isn't a good idea.You only need to change the wxFrame style according to your needs.
In this special case, yes, I agree, but it may exist cases where we need to go wild way (don't follow the standard)... And it can be important to be able to be not constraint by a tool (here, wxSmith). So, how, if I want to base an app on a class of mine using wxSmith ? Is that possible ? Or should I use wxFormBuilder rather ?