Firstly, I do agree that the warnings are annoying, I certainly did not like getting those wxFont ctor warning when using older wxFormBuilder back then. But they do have a purpose, i.e., to make you stop using code that may be error-prone and is going to be removed sooner or later.
Secondly, the updated wizard I provide along my guide does not produce any C++ code. It shows the wizard dialog and sets the project settings. The C++ code is provided by the Code::Blocks template, which can be found in the C::B install folder (e.g.,
C:\Program Files\CodeBlocks\) in folder
share\CodeBlocks\templates\wizard\wxwidgets and I did not modify it in any way.
Secondly, there are no deprecation warnings for the program generated by the wizard as described in my guide:
------------- Build: Debug in Test321b (compiler: msys2-mingw-w64-x86_64)---------------
windres.exe -ID:\Dev\Desktop\!Lib\wxWidgets-3.2.1\include -ID:\Dev\Desktop\!Lib\wxWidgets-3.2.1\lib\gcc_dll-x64\mswud -J rc -O coff -i C:\dev\cb-tests\Test321b\resource.rc -o obj\Debug\resource.res
g++.exe -pipe -mthreads -D__GNUWIN32__ -D__WXMSW__ -DWXUSINGDLL -DwxUSE_UNICODE -Wall -g -D__WXDEBUG__ -ID:\Dev\Desktop\!Lib\wxWidgets-3.2.1\include -ID:\Dev\Desktop\!Lib\wxWidgets-3.2.1\lib\gcc_dll-x64\mswud -c C:\dev\cb-tests\Test321b\Test321bApp.cpp -o obj\Debug\Test321bApp.o
g++.exe -pipe -mthreads -D__GNUWIN32__ -D__WXMSW__ -DWXUSINGDLL -DwxUSE_UNICODE -Wall -g -D__WXDEBUG__ -ID:\Dev\Desktop\!Lib\wxWidgets-3.2.1\include -ID:\Dev\Desktop\!Lib\wxWidgets-3.2.1\lib\gcc_dll-x64\mswud -c C:\dev\cb-tests\Test321b\Test321bMain.cpp -o obj\Debug\Test321bMain.o
g++.exe -LD:\Dev\Desktop\!Lib\wxWidgets-3.2.1\lib\gcc_dll-x64 -o bin\Debug\Test321b.exe obj\Debug\Test321bApp.o obj\Debug\Test321bMain.o obj\Debug\resource.res -mthreads -lwxmsw32ud_webview -lwxmsw32ud_stc -lwxmsw32ud_propgrid -lwxmsw32ud_ribbon -lwxmsw32ud_richtext -lwxmsw32ud_xrc -lwxmsw32ud_aui -lwxmsw32ud_media -lwxbase32ud_net -lwxmsw32ud_gl -lwxbase32ud_xml -lwxmsw32ud_adv -lwxmsw32ud_html -lwxmsw32ud_core -lwxbase32ud -mwindows
Output file is bin\Debug\Test321b.exe with size 907.71 KB
Process terminated with status 0 (0 minute(s), 4 second(s))
0 error(s), 0 warning(s) (0 minute(s), 4 second(s))
This is hardly surprising, as the generated code does not use the deprecated wxFont constructor nor does it attempt to create a wxTimerEvent instance. But neither does your code posted above, so I have no idea where your warnings come from.
Thirdly, I would not be surprised if wxSmith did generate outdated code. AFAIK, the plugin is not maintained much and may even lack support for newer wxWidgets classes (such as ribbon, webview, stc, or propgrid). I myself never used it, I use wxFormBuilder. However, I tried changing the font for a button and wxSmith did generate the correct ctor.
EDIT
Sorry, I only now realized that you did not use wxSmith (used by default in the guide) but chose wxFormBuilder so my wxSmith comments are irrelevant. The rest still stands though.