wxpy 2.7 problem

I still have both wxpy2.6.3.3 and wxpy 2.7.0.0 on my machine with their respective demos packages. In the KeyEvent sample I get KeyCode 347 with 2.6.3.3 and KeyCode 345 with the 2.7 demo.

Marco

Right, but does it display the correct F-key constant for each, or does one of them display some other key name?

···

m.prosperi@libero.it wrote:

I still have both wxpy2.6.3.3 and wxpy 2.7.0.0 on my machine with
their respective demos packages. In the KeyEvent sample I get KeyCode
347 with 2.6.3.3 and KeyCode 345 with the 2.7 demo.

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

Robin Dunn wrote:

I still have both wxpy2.6.3.3 and wxpy 2.7.0.0 on my machine with
their respective demos packages. In the KeyEvent sample I get KeyCode
347 with 2.6.3.3 and KeyCode 345 with the 2.7 demo.

Right, but does it display the correct F-key constant for each, or does one of them display some other key name?

I see the same thing, on Windows XP with Python 2.5 final and wxPython 2.7.0.1pre.20060909 I get:
Event Type Key Name Key Code Modifiers Unicode RawKeyCode RawKeyFlags KeyDown WXK_F6 345 ---- 117 117 4194305 Char WXK_F6 345 ---- 117 117 4194305 KeyUp WXK_F6 345 ---- 117 117 3225419777

And with Python 2.4 and wxPython 2.6.3 I get:
Event Type Key Name Key Code Modifiers Unicode RawKeyCode RawKeyFlags KeyDown WXK_F6 347 ---- 0 117 4194305 Char WXK_F6 347 ---- 0 117 4194305 KeyUp WXK_F6 347 ---- 0 117 3225419777

Werner

···

m.prosperi@libero.it wrote:

Werner F. Bruhin wrote:

Robin Dunn wrote:

I still have both wxpy2.6.3.3 and wxpy 2.7.0.0 on my machine with
their respective demos packages. In the KeyEvent sample I get KeyCode
347 with 2.6.3.3 and KeyCode 345 with the 2.7 demo.

Right, but does it display the correct F-key constant for each, or does one of them display some other key name?

I see the same thing, on Windows XP with Python 2.5 final and wxPython 2.7.0.1pre.20060909 I get:
Event Type Key Name Key Code Modifiers Unicode RawKeyCode RawKeyFlags KeyDown WXK_F6 345 ---- 117 117 4194305 Char WXK_F6 345 ---- 117 117 4194305 KeyUp WXK_F6 345 ---- 117 117 3225419777

And with Python 2.4 and wxPython 2.6.3 I get:
Event Type Key Name Key Code Modifiers Unicode RawKeyCode RawKeyFlags KeyDown WXK_F6 347 ---- 0 117 4194305 Char WXK_F6 347 ---- 0 117 4194305 KeyUp WXK_F6 347 ---- 0 117 3225419777

So you are getting WXK_F6 for each. So what is the problem? The point of having constants like this is that the *value* of the constant can change without the code using the name of the constant caring about it.

···

m.prosperi@libero.it wrote:

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!

Robin Dunn wrote:

Werner F. Bruhin wrote:

Robin Dunn wrote:

I still have both wxpy2.6.3.3 and wxpy 2.7.0.0 on my machine with
their respective demos packages. In the KeyEvent sample I get KeyCode
347 with 2.6.3.3 and KeyCode 345 with the 2.7 demo.

Right, but does it display the correct F-key constant for each, or does one of them display some other key name?

I see the same thing, on Windows XP with Python 2.5 final and wxPython 2.7.0.1pre.20060909 I get:
Event Type Key Name Key Code Modifiers Unicode RawKeyCode RawKeyFlags KeyDown WXK_F6 345 ---- 117 117 4194305 Char WXK_F6 345 ---- 117 117 4194305 KeyUp WXK_F6 345 ---- 117 117 3225419777

And with Python 2.4 and wxPython 2.6.3 I get:
Event Type Key Name Key Code Modifiers Unicode RawKeyCode RawKeyFlags KeyDown WXK_F6 347 ---- 0 117 4194305 Char WXK_F6 347 ---- 0 117 4194305 KeyUp WXK_F6 347 ---- 0 117 3225419777

So you are getting WXK_F6 for each. So what is the problem? The point of having constants like this is that the *value* of the constant can change without the code using the name of the constant caring about it.

I was just confirming the OP's finding, but you are obviously right one should not care about the value. But maybe still worth a small note in the changes list?

Werner

···

m.prosperi@libero.it wrote:

Werner F. Bruhin wrote:

Robin Dunn wrote:

So you are getting WXK_F6 for each. So what is the problem? The point of having constants like this is that the *value* of the constant can change without the code using the name of the constant caring about it.

I was just confirming the OP's finding,

Sorry, I wasn't paying close enough attention, I thought that you were the OP.

···

--
Robin Dunn
Software Craftsman
http://wxPython.org Java give you jitters? Relax with wxPython!