2.6=>2.8 (windows) - wxHorror :/

wxPython Users
1

Hello!

I use wxPython in my job and i like it very much. Our application is very complicated. A when i switch from version 2.6 to 2.8 i have some problems :frowning:

  1. navigation keys from numpad - now only EVT_CHAR get old keycodes (WXK_UP etc), in EVT_KEY_DOWN/UP i get only new WXK_NUMPAD_xxxx

  2. some troubles with julian date (i use only whole days without time) - in 2.6 i got for example GetJDN()==2.5, and now this same date==2.485 - and finally i get wrong result date - i use now ResetTime() for better way (i get xxxx.xx.xx 01:00:00, with 2.6 i got 00:00:00 time)

  3. very strange error - http://www.nabble.com/Strange-behaviour-with-wxBitmapButton-in-2.8.0-RC1-t2767193.html
    . When i run app under XP without skin all is ok, but wiht themes every bitmapbutton have border - i found this page and use style=wx.NO_BORDER. But in help i don’t found any information about this style for wxBitmapButton. Under ver. 2.6 all ok

  4. I wxPython demo is custom tree demonstration but label editing is not possible - this control need need_chars flag - wihout this enter key don’t work… Double click on demo navigation tree throw some error on my console

I have some work with this version revolution - i have some troubles with events in my custom controls. I write probably something else about my wxAdventures :slight_smile:

I still love this library - but sometimes use this is harmful for my health :wink:

Sorry for my eng :confused:

w.

2

Wojtek P wrote:

Hello!

I use wxPython in my job and i like it very much. Our application is very complicated. A when i switch from version 2.6 to 2.8 i have some problems :frowning:

1) navigation keys from numpad - now only EVT_CHAR get old keycodes (WXK_UP etc), in EVT_KEY_DOWN/UP i get only new WXK_NUMPAD_xxxx

I think the current behavior is correct. The KEY_UP/DOWN events are supposed to give you a unique (raw) value for the key itself, not necessarily the same as the (cooked) value the key is supposed to represent. In other words in this case it's a numpad key so you'll get the WXK_NUMPAD_UP code for the key events, but the key is intended to be used for either an up arrow or an 8, so you get WXK_UP or 8 for the char event.

2) some troubles with julian date (i use only whole days without time) - in 2.6 i got for example GetJDN()==2.5, and now this same date==2.485 - and finally i get wrong result date - i use now ResetTime() for better way (i get xxxx.xx.xx 01:00:00, with 2.6 i got 00:00:00 time)

Can you provide some sample code that shows this problem?

3) very strange error - http://www.nabble.com/Strange-behaviour-with-wxBitmapButton-in-2.8.0-RC1-t2767193.html. When i run app under XP without skin all is ok, but wiht themes every bitmapbutton have border - i found this page and use style=wx.NO_BORDER. But in help i don't found any information about this style for wxBitmapButton. Under ver. 2.6 all ok

Because it's not a wxBitmapButton specific style, it is a general border style that can be used with any widget type. Each widget however is able to use or ignore border styles as they see fit.

4) I wxPython demo is custom tree demonstration but label editing is not possible - this control need need_chars flag - wihout this enter key don't work... Double click on demo navigation tree throw some error on my console

There was a workaround for this shown in a message yesterday about navigation key events.

···

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

3
  1. some troubles with julian date (i use only whole days without time) -

in 2.6 i got for example GetJDN()==2.5, and now this same date==2.485 -
and finally i get wrong result date - i use now ResetTime() for better
way (i get xxxx.xx.xx 01:00:00, with 2.6 i got 00:00:00 time)

Can you provide some sample code that shows this problem?

import wx
import wx._misc as misc
import sys

print “\n\n Python”,sys.version
print " wxPython",
wx.VERSION_STRING,“\n”

test_date = misc.DateTimeFromDMY(1,1,2001) # 01.01.2001
print " test_date",test_date
test_jdn = test_date.GetJDN()
print " test_date.GetJDN()",test_jdn

Results:

Python 2.4.2 (#67, Sep 28 2005, 12:41:11) [MSC v.1310 32 bit (Intel)]

wxPython 2.6.1.0

test_date 02/01/01 00:00:00

test_date.GetJDN() 2451941.5

Python 2.4.4 (#71, Oct 18 2006, 08:34:43) [MSC v.1310 32 bit (Intel)]

wxPython 2.8.4.2

test_date 02/01/01 00:00:00

test_date.GetJDN() 2451941.45833

4

Wojtek P wrote:

     >
     > 2) some troubles with julian date (i use only whole days without
    time) -
     > in 2.6 i got for example GetJDN()==2.5, and now this same
    date==2.485 -
     > and finally i get wrong result date - i use now ResetTime() for
    better
     > way (i get xxxx.xx.xx 01:00:00, with 2.6 i got 00:00:00 time)

    Can you provide some sample code that shows this problem?

import wx
import wx._misc as misc
import sys

print "\n\n Python",sys.version
print " wxPython", wx.VERSION_STRING,"\n"

test_date = misc.DateTimeFromDMY(1,1,2001) # 01.01.2001
print " test_date",test_date
test_jdn = test_date.GetJDN()
print " test_date.GetJDN()",test_jdn

Results:

# Python 2.4.2 (#67, Sep 28 2005, 12:41:11) [MSC v.1310 32 bit (Intel)]
# wxPython 2.6.1.0 <http://2.6.1.0>
# test_date 02/01/01 00:00:00
# test_date.GetJDN() 2451941.5

# Python 2.4.4 (#71, Oct 18 2006, 08:34:43) [MSC v.1310 32 bit (Intel)]
# wxPython 2.8.4.2 <http://2.8.4.2>
# test_date 02/01/01 00:00:00
# test_date.GetJDN() 2451941.45833

One of the change logs mentioned fixing a bunch of Time Zone related bugs. Perhaps this difference is related to that? If not then please enter a bug report about it using the "Common" category.

···

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