Attached is sample code to demonstrate an effect that is disastrous for my
application. If the user sets the checkbox and then presses the TAB or ENTER
key more than once, the onCellChange event triggers each time, even though
nothing has changed. This happens with version 2.2.9 on debian woody. I have
a workaround, but if this behavior has changed in a newer version, it will be
another reason to upgrade.
With due appreciation to the incredible amount of work that has gone into
wxPython, this experience raises an issue about one feature of the grid that
is not traditional and is somewhat of an annoyance. It is that the CELL_CHANGE
event is tied to the SELECT_CELL event. If the user forgets to move to
another cell or press an appropriate key before leaving the grid to
click on a processing button, the last entry is lost. Ideally there should be
an additional event, such as a depart-cell or lost-focus event, on which to
hang CELL_CHANGE. This would also offer an alternate chance to validate an
entry. Not knowing how to do it myself, I find it easy to recommend but do
believe such a change would add to the user-friendliness of an application.
Attached is sample code to demonstrate an effect that is disastrous for my
application. If the user sets the checkbox and then presses the TAB or ENTER
key more than once, the onCellChange event triggers each time, even though nothing has changed. This happens with version 2.2.9 on debian woody. I have
a workaround, but if this behavior has changed in a newer version, it will be
another reason to upgrade.
It still does it. Please enter a bug report about it.
With due appreciation to the incredible amount of work that has gone into
wxPython, this experience raises an issue about one feature of the grid that
is not traditional and is somewhat of an annoyance. It is that the CELL_CHANGE
event is tied to the SELECT_CELL event. If the user forgets to move to another cell or press an appropriate key before leaving the grid to
click on a processing button, the last entry is lost. Ideally there should be
an additional event, such as a depart-cell or lost-focus event, on which to
hang CELL_CHANGE. This would also offer an alternate chance to validate an entry. Not knowing how to do it myself, I find it easy to recommend but do
believe such a change would add to the user-friendliness of an application.
That does make sense. Please enter a feature request.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!