Hi all.
I'm working with wxPython, testing project Phoenix with wxFormBuidler (3.3.4-beta).
I try the AUI but when I generate the python source code, wxFormBuilder produces wx.aui reference, while the aui library is locate under wx.lib.agw.
wx.aui and wx.lib.agw.aui are not the same. The first is the wxWidget C++ version and the second is Andrea's Python implementation of the first one.
So wxFormBuilder has to write wx.lib.agw.aui instead wx.aui in the final file.
I have to way
1. make "the alias" wx.aui which point to wx.lib.agw.aui so the code from wxFormBuilder is compatible with Phoenix.
2. change the production of wxFormBuilder to make the right reference to aui.
You need to "teach" wxFB to know the differences and allow you to use one or the other.
Hi all.
I'm working with wxPython, testing project Phoenix with wxFormBuidler
(3.3.4-beta).
I try the AUI but when I generate the python source code, wxFormBuilder
produces wx.aui reference, while the aui library is locate under wx.lib.agw.
So wxFormBuilder has to write wx.lib.agw.aui instead wx.aui in the final
file.
I have to way
1. make "the alias" wx.aui which point to wx.lib.agw.aui so the code
from wxFormBuilder is compatible with Phoenix.
2. change the production of wxFormBuilder to make the right reference to
aui.
Which is the best choice?
The wx.aui package will probably end up in Phoenix eventually, although I have been considering leaving it out since wx.agw.aui is better maintained. Perhaps the best thing would be to get wxFormBuilder to be able to support using either. It's been a while since I've used FB, do they already have the ability to add and use custom Python-only widgets in the designer?