Steffen Olszewski

In fact all elements you can use in wxFB are realized as plugins. A plugin consists of two parts: the xml file(s) that describe its elements together with the template...

This sounds quite familiar and i'm afraid this is caused by wxWidgets 3.0, i can't reproduce this with my current wxWidgets 3.1 build. If you have the possibility, build a...

As can be seen in your backtracke, it is the issue 😉. I can also confirm your observations of the other packages you used. The deb package you can download...

Seems to be possible, a little difficulty might be that these meta elements are used for wxToolBar and wxAuiToolBar together and the former does not support a proportion but the...

This is most probably a problem of wxScintilla or wrong usage of that one, i see this issue in e.g. CodeBlocks as well. As workaround you can put the cursor...

I don't know any Python nor the Python port of wxWidgets, but the original C++ library does not contain such a class. So either this is a Python only control...

Since MSYS2 ships a wxWidgets 3.1 release the GitHub CI is using it and there was never a problem finding it. In what situations does this not work? Looking at...

If thats the case it seems the best way to solve this is to set the environment variable WX_CONFIG to the required version, the Find Module should work without any...

There is no expression parser inside wxFormBuilder, values are usually used as-is. In these days you should not use static ids for your widgets anymore (except stock ids), just use...

The wxFB datamodel only allows the type container as child element for wxSplitter although that control only requires a wxWindow. It seems this is also the case for certain other...