Is there a limit to the number of bindings we can make not to the frame but to the single control?
To explain the sense of my question, I subclassed a wx.ComboBox, and inside the class there’s a self.Bind(wx.EVT_COMBOBOX…).
When using this subclass in an application, I put another myCombo.Bind(wx.EVT_COMBOBOX…), and the binding did not work.
I replaced the second binding with a self.Bind(wx.EVT_COMBOBOX, self.OnEVT_COMBOBOX, myCombo) and now it works.
Raffaello Barella wrote:
Is there a limit to the number of bindings we can make not to the frame but to the single control?
To explain the sense of my question, I subclassed a wx.ComboBox, and inside the class there's a self.Bind(wx.EVT_COMBOBOX...).
When using this subclass in an application, I put another myCombo.Bind(wx.EVT_COMBOBOX...), and the binding did not work.
I replaced the second binding with a self.Bind(wx.EVT_COMBOBOX, self.OnEVT_COMBOBOX, myCombo) and now it works.
There is no limit, but by default the search for an event handler stops when a handler is found. To tell the event system to keep looking, you just need to call event.Skip in the handler(s) that do get called.
--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!