A quick search couldn't find a mention of this problem so I thought I would raise it here. It seems that binding spin events (EVT_SPINCTRL, EVT_SPIN, EVT_SPIN_UP and EVT_SPIN_DOWN) doesn't work with wxPython 2.4.0.7 on Linux.
This was first spotted in PythonCard, but I've knocked a quick sample (see attachment). This works on Windows, printing out 'Current value of spin is ..." but produces nothing in the console window on my Linux box.
Environment : Debian testing, Python 2.2.2 and wxPython 2.4.0.7 (actually called libwxgtk2.4-python 2.4.0.8).
A quick search couldn't find a mention of this problem so I thought I would raise it here. It seems that binding spin events (EVT_SPINCTRL, EVT_SPIN, EVT_SPIN_UP and EVT_SPIN_DOWN) doesn't work with wxPython 2.4.0.7 on Linux.
This was first spotted in PythonCard, but I've knocked a quick sample (see attachment). This works on Windows, printing out 'Current value of spin is ..." but produces nothing in the console window on my Linux box.
Environment : Debian testing, Python 2.2.2 and wxPython 2.4.0.7 (actually called libwxgtk2.4-python 2.4.0.8).
For me your sample does nothing on both wxMSW and wxGTK (2.4.1.2) but changing it to EVT_SPINCTRL works on both platforms, as it is supposed to.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
A quick search couldn't find a mention of this problem so I thought I
would raise it here. It seems that binding spin events (EVT_SPINCTRL,
EVT_SPIN, EVT_SPIN_UP and EVT_SPIN_DOWN) doesn't work with wxPython
2.4.0.7 on Linux.
al of those events, except EVT_SPINCTRL, are for wxSpinButton, not
wxSpinCtrl, which you are using. Using EVT_SPINCTRL works just fine for
me. Also, binding the event in the App is a bit strange. I moved it to
the frame which is probalbay a better place to put it. I"ve enclosed my
altered and functional version.