[wxPython] Demo bugs

I just downloaded wxPython-2.2.2-Py20.EXE and played
a bit with the demo.

I have a couple of problems.

Both ActiveX demos crash the demo for me (illegal
page fault, or illegal stack fault). I'm running
Python 2.0 win32all build 135 and Win98SE.
Checking the bug database I see this is reported
as Bug #122100. No 'proper' solution yet?

Also, there are some flaws in both calendar controls.
In both the C++ and Python versions, you can *type* in
another year in the year-field, and the result won't
be reflected in the calendar. You have to use the
sliders even though the year fields are not read-only.
I'd prefer that the controls handled manually entered
years, but if not I guess they should be read-only. For the
Python version, the same problem exists for the month.
(In the C++ version, if you want a calendar for February
year 2201 and don't want to click on a button 200 times,
you can type 2200 and click once to increment one year.
This doesn't work with the Python version--but it's an
ugly workaround anyway...)

Running the slashdot demo made the whole demo app
unresponsive to input. (I couldn't ping slashdot.org
at that time, so thee was some internet problem.)
Anyway, I had to crtl-alt-del to get out of that.
(Maybe I could have waited a few more minutes...)

I also have problems with memory leaks. After I
played with the demos for a while (with above mentioned
problems) I could no longer restart it--out of memory.
I don't know if it's connected to the Active X crashes
or the Slashdot ctrl-alt-del or something else.

Still, it looks really nice, and I hope to get back
with a fixed calendar control when I get time, if
noone beats me to it...

/Magnus Lyckå

Regarding the ActiveX problems-- on my box it seems to have been resolved
with wxPython 2.2.5.

Dan

···

----- Original Message -----
From: "Magnus Lycka" <magnus@thinkware.se>
To: <wxpython-users@lists.sourceforge.net>
Sent: Tuesday, February 06, 2001 6:21 PM
Subject: [wxPython] Demo bugs

I just downloaded wxPython-2.2.2-Py20.EXE and played
a bit with the demo.

[...]

Both ActiveX demos crash the demo for me (illegal
page fault, or illegal stack fault). I'm running
Python 2.0 win32all build 135 and Win98SE.
Checking the bug database I see this is reported
as Bug #122100. No 'proper' solution yet?

[...]

_______________________________________________
wxPython-users mailing list
wxPython-users@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/wxpython-users

Regarding the ActiveX problems-- on my box it seems to have been resolved
with wxPython 2.2.5.

It still crashes for me.

Did it crash for you before? What version of Windows are you running?
BeOpen or ActiveState Python? Which version of win32all?

···

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

_______________________________________________
wxPython-users mailing list
wxPython-users@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/wxpython-users