[wxPython] wxGrid, cell editing with non-US keyboard

wxPython Users
1

Hi Stefan,

Stefan wrote:

It is? What exactly are you talking about? If it's the first character
which auto-starts editing not always getting correctly into the
cell, then there's nothing I can suggest but getting used to start
editing by pressing F2....

1) Yes, it is exactly that problem. I am sorry to say, but pressing F2
is not a valid argument. Using F2 may be ok, if you want to enter
text in a small number of cells, but not if you enter hundreds of
words. I'm speaking french and german (Stefan sounds german?),
you can not imagine the number of words starting with an accentuated
letter or starting with an 'Umlauted' letter.
Besides this, the F2 key may be reserved for frame navigation.

2) I tried to solve the problem, by writing my own cell editing in
a seperate wxTextControl. In that case, I'm falling into one another
problem. Because of your embedded in-cell editing, I can not
(or I do not succeed to) catch grid events like keyup, onchar, ....
Desabling the cell editing will not help. It does not make
these events alive. Using wxPython, I have tried things
like EVT_KEY_DOWN(self.GetGridWindow(), self.OnKeyDown)
but .... Is there doc about such events?

3) wxGrid is a very complexe widget/control, may be too much.
Why not provide a "wxSimpleGrid" control with a limited number of
methods, attributes, but that can catch all standard events?
An event char may be used for a task, that not fires editing.
I'm pretty sure, a lot of developpers be will happy with this.
There is wxStyledTextControl, but a wxTextControl.

And you, wxPython developpers, what do you think about this?
cc to wxpython-users list

Congrats for the 2.3.3.1 (wxWindow team and Robin)

Regards
Jean-Michel Fauth, Switzerland

2

I thought this was solved in 2.3.3. At least I can start editing
in the demo with åäö. I notice that I can't start editing by
composing with accent keys, like ´e to get é, or ¨u to get ü.
But otherwise this seems to have been solved, for which I'm
very thankful. This *was* a serious bug from a Scandinavian
perspective.

My client refused F2, and decided to use [Enter] to enter the
cell. After a while he got really tired of that, so I'm very
happy that it works with åäö now.

I can certainly understand the frustration for people who
regularly use things like ô, é or ü but don't have keys for that.

I also noticed that I can't start editing with charcters that
require AltGr (that's right Alt-key on our keyboard, same as
Ctrl-Alt), such as @, $, {, }, [, ], \, | or € (euro sign).
But maybe that's easy to fix. I didn't make a serious attempt.
(It works in Excel though! :wink:

I understand the problems here. It's not as if the users of
wxPython/wxWindows are paying massive licence fees to the
developers, but this is certainly a kind of behaviour that
could make a customer really upset. Looking back to earlier
customers I can well imagine some who completely would have
refused to accept an application with the current behaviour
in grids.

/Magnus

P.S. I hope this isn't all gibberish. I just came home from
testing Lagavulin 16 yo, Bowmore 30 yo & Caol Ila 15 yo...
As usual we ended the evening with a few beers...

···

At 11:38 2002-09-21 +0200, Jean-Michel Fauth wrote:

Stefan wrote:
> It is? What exactly are you talking about? If it's the first character
> which auto-starts editing not always getting correctly into the
> cell, then there's nothing I can suggest but getting used to start
> editing by pressing F2....

1) Yes, it is exactly that problem.

--
Magnus Lyckå, Thinkware AB
Älvans väg 99, SE-907 50 UMEÅ
tel: 070-582 80 65, fax: 070-612 80 65
http://www.thinkware.se/ mailto:magnus@thinkware.se