When calling methods in wxPython which are intended to extend the fuctionality of an event handler, it appears as though one must take stack depth in to consideration. For example, I tried:[CODE=python]#
def CloseSession(se lf, event):
sib = self.sibbling
pos = self.GetPositio n()
sib.Move(pos)
sib.Show()
self.Hide()
### allow event processing to continue here ###
event.Skip()
def OnFeatureDialog Close(self, event):
self.CloseSessi on(event)[/CODE]
which seems like it should work, but doesn't.
So use:[CODE=python]#
def CloseSession(se lf):
sib = self.sibbling
pos = self.GetPositio n()
sib.Move(pos)
sib.Show()
self.Hide()
def OnFeatureDialog Close(self, event):
self.CloseSessi on()
### allow event processing to continue here ###
event.Skip()[/CODE]
to get the correct internal reaction to the wx.EVT_CLOSE.
def CloseSession(se lf, event):
sib = self.sibbling
pos = self.GetPositio n()
sib.Move(pos)
sib.Show()
self.Hide()
### allow event processing to continue here ###
event.Skip()
def OnFeatureDialog Close(self, event):
self.CloseSessi on(event)[/CODE]
which seems like it should work, but doesn't.
So use:[CODE=python]#
def CloseSession(se lf):
sib = self.sibbling
pos = self.GetPositio n()
sib.Move(pos)
sib.Show()
self.Hide()
def OnFeatureDialog Close(self, event):
self.CloseSessi on()
### allow event processing to continue here ###
event.Skip()[/CODE]
to get the correct internal reaction to the wx.EVT_CLOSE.