I have a grid & gridtablebase that are working as expected ... except for the wxGridCellBoolEditor.
Unfortunately I can't reproduce the problem into a test example.
The boolean editor works normally when the grid is run in a test frame, but when it is part of the application, it 'eats' all Key Events.
When the editor is active, no EVT_KEY_DOWN events are generated. The enter and tab keys don't allow you out of the cell. One way to get the editor to finish and set the new value is to mouse click on another cell. The focus appears on other buttons on the page when the tab key is pressed, but it doesn't finish the editor.
The left and up arrows do close the editor, after cycling focus through all the buttons on the page. The right and down buttons only cycle focus, without ever closing the editor. There is another button on the same panel as the grid. The left & up arrows skip this button. The right & down arrows don't skip this button.
I don't have any more ideas about how to break this problem down without pulling the app apart line by line (too many files with too many lines and not enough days in the year)
Any suggestions on where to look, or how to write a simple boolean editor?
I have a grid & gridtablebase that are working as expected ... except
for the wxGridCellBoolEditor.
Unfortunately I can't reproduce the problem into a test example.
The boolean editor works normally when the grid is run in a test
frame, but when it is part of the application, it 'eats' all Key
Events.
When the editor is active, no EVT_KEY_DOWN events are generated. The
enter and tab keys don't allow you out of the cell. One way to get
the editor to finish and set the new value is to mouse click on
another cell. The focus appears on other buttons on the page when the
tab key is pressed, but it doesn't finish the editor.
The left and up arrows do close the editor, after cycling focus
through all the buttons on the page. The right and down buttons only
cycle focus, without ever closing the editor. There is another button
on the same panel as the grid. The left & up arrows skip this button.
The right & down arrows don't skip this button.
Try this: don't put the grid on a panel. The panel is trying to implement tab (and other navigation key) traversal and so is messing up the grid's handling of the nav keys. Instead, put the grid directly on the frame, and also put your panel (with it's other controls) directly on the frame and use a sizer to manage the layout of the grid and panel.
···
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
The grid works fine on a panel on a frame. When thrown into the app, I use a frame with splitter window, then use the panel et al (for switching windows I've subclassed panels with the controls etc). Thats when it doesn't work quite as expected.
I've had a temp hold up in that wxGlade hasn't allowed me to pull the grid off as a separate class yet (and I've not had time to do it manually).
I'll have to rethink the window switching if the grid isn't on a panel. Oh the fun of it all.
Any other suggestions of how to takle this are appreciated.
Chris.
···
----- Original Message -----
From: Robin Dunn
To: wxPython-users@lists.wxwindows.org
Sent: Tuesday, April 01, 2003 8:02 AM
Subject: Re: [wxPython-users] Help with wxGridCellBoolEditor
Chris Munchenberg wrote:
I have a grid & gridtablebase that are working as expected ... except
for the wxGridCellBoolEditor.
Unfortunately I can't reproduce the problem into a test example.
The boolean editor works normally when the grid is run in a test
frame, but when it is part of the application, it 'eats' all Key
Events.
When the editor is active, no EVT_KEY_DOWN events are generated. The
enter and tab keys don't allow you out of the cell. One way to get
the editor to finish and set the new value is to mouse click on
another cell. The focus appears on other buttons on the page when the
tab key is pressed, but it doesn't finish the editor.
The left and up arrows do close the editor, after cycling focus
through all the buttons on the page. The right and down buttons only
cycle focus, without ever closing the editor. There is another button
on the same panel as the grid. The left & up arrows skip this button.
The right & down arrows don't skip this button.
Try this: don't put the grid on a panel. The panel is trying to
implement tab (and other navigation key) traversal and so is messing up
the grid's handling of the nav keys. Instead, put the grid directly on
the frame, and also put your panel (with it's other controls) directly
on the frame and use a sizer to manage the layout of the grid and panel.
--
Robin Dunn
Software Craftsman http://wxPython.org Java give you jitters? Relax with wxPython!
---------------------------------------------------------------------
To unsubscribe, e-mail: wxPython-users-unsubscribe@lists.wxwindows.org
For additional commands, e-mail: wxPython-users-help@lists.wxwindows.org