Why I will stop using wxPython

How would I try to repro this grid editing problem on my US keyboard? Is it even possible or will I need a non-US keyboard to see it? Is it Windows-only? If Windows-only, is it only specific versions of Windows?

Is there a simple test script posted anywhere that demos the problem?

How many people actually release applications where you allow users to edit values with a grid control? I've always considered grids to really be read-only record-selecting controls - if you want to edit a value you do that on a separate frame (for instance, that pops up when you press <enter> on the grid row). Then again, I'm coming from a database-app perspective - I can see wanting to edit the grid cells directly in more of a spreadsheet-app design.

I'm not trying to belittle the problem - merely trying to understand the scope of it better. At the very least, we need to document where and when this problem manifests itself, if that hasn't already been done.

ยทยทยท

--
pkm ~ http://paulmcnett.com

Paul McNett wrote:

Is it Windows-only?

I think so.

If Windows-only, is it only specific versions of Windows?

Same problem with Win98, Win2k and XP at least.

How many people actually release applications where you allow users to edit values with a grid control? I've always considered grids to really be read-only record-selecting controls - if you want to edit a value you do that on a separate frame (for instance, that pops up when you press <enter> on the grid row). Then again, I'm coming from a database-app perspective - I can see wanting to edit the grid cells directly in more of a spreadsheet-app design.

I built an app for a customer a few years ago, which was mainly based on editing in grids (five of them).

I'm not trying to belittle the problem - merely trying to understand the scope of it better. At the very least, we need to document where and when this problem manifests itself, if that hasn't already been done.

I think wxWidgets developers such as Vadim Zeitlin know what it's about.