wxSplitterWindow idle event handler for Python

[tester0077]

The current event handler code for the splitter causes a crash when exiting a python app using the code from wxFB which includes a splitter.
As I am very new to (wx)Python, I have no idea if or how this can be fixed. Any help or comments will be much appreciated.

The generated code:

def m_splitter2OnIdle( self, event ):
        self.m_splitter2.SetSashPosition( 0 )
        self.m_splitter2.Unbind( wx.EVT_IDLE )

with the error

d:\pkg\python\wxFB\wxPython\wpMeta\wpMeta.py' 
Traceback (most recent call last):
  File "d:\pkg\python\wxFB\wxPython\wpMeta\wpMetaBase.py", line 170, in m_splitter2OnIdle
    self.m_splitter2.SetSashPosition( 0 )
RuntimeError: wrapped C/C++ object of type SplitterWindow has been deleted
Traceback (most recent call last):
  File "d:\pkg\python\wxFB\wxPython\wpMeta\wpMetaBase.py", line 170, in m_splitter2OnIdle
    self.m_splitter2.SetSashPosition( 0 )
RuntimeError: wrapped C/C++ object of type SplitterWindow has been deleted
Traceback (most recent call last):
  File "d:\pkg\python\wxFB\wxPython\wpMeta\wpMetaBase.py", line 170, in m_splitter2OnIdle
    self.m_splitter2.SetSashPosition( 0 )
RuntimeError: wrapped C/C++ object of type SplitterWindow has been deleted
Traceback (most recent call last):
  File "d:\pkg\python\wxFB\wxPython\wpMeta\wpMetaBase.py", line 170, in m_splitter2OnIdle
    self.m_splitter2.SetSashPosition( 0 )
RuntimeError: wrapped C/C++ object of type SplitterWindow has been deleted
Traceback (most recent call last):
  File "d:\pkg\python\wxFB\wxPython\wpMeta\wpMetaBase.py", line 170, in m_splitter2OnIdle
    self.m_splitter2.SetSashPosition( 0 )
RuntimeError: wrapped C/C++ object of type SplitterWindow has been deleted

[sodevel]

I don't know any Python at all or how the wxWidgets language binding does work, so i can only guess here. This event handler should be called only once during idle time, apparently it gets called too late, after the C++ side got cleaned up. Or maybe too early, when the C++ side isn't initialized yet? Do you initialize wxWidgets properly? To you create or delete your Python objects at the wrong time? In C++ e.g. you cannot use most wxWidgets components as static class members because the will get used before wxWidgets is initialized, maybe some problem like this exists in Python as well.

[tester0077]

After looking at the code some more, it looks like it ought to unbind itself after the first call, and yet it seems to get called 5 times in a row. Seems like the unbind is never actually executed.
Unfortunately, after running into this issue, I removed the code in my current app to avoid the crash.
I have just added another splitter and the splitterxOnIdle is called very time the mouse enters the main frame, which confirms my suspicion, but at this stage and with my current understanding of Python and wxFormBuilder, I am unable to debug it into the unbind call.

[tester0077]

Eventually, I recalled from, my work long ago, when I was using wxFB for my C++ projects, that it adds its own OnIdle handler, which it immediately removed. Hence for C++ I had to add my own OnIdle handler if I wanted this feature to work with my own needs. As

[tester0077]

There is a similar issue (IMO) discussed @: https://stackoverflow.com/questions/25712775/wxpython-unbind-method-returns-true-but-doesnt-unbind

[tester0077]

I have now raised the issue on the wxPython forum, because it looks to me as though the problem is with wxPython not unbinding the handler