[wxPython] grid-problem with 2.3.1/MSW98 ?

I still use wxPython2.2.2/MSW98/Python2.0.
Trying to use 2.3.1 I've some difficulties, if I recreate dialogs with a
grid inside.
I've menue for changing the display language (german/english/...), so I
.Destroy()
all the old windows
(splitter/tree,notebook/scrolledwindow/controls,grid(s))
and recreate them new.
That's running well with 2.2.2 but with 2.3.1 after several
menue-actions (10 or more)
the background greys and the controls and grids are crippled. I can
close my
program and call it again, than I don't need any trials it's bad from
the beginning,
also some other MSW-applications have the same "decorations" (I've to
reboot).
The result of my trials is that it must displayed a grid, than it
happens, but sure I'm not.

Thanks, Udo

I still use wxPython2.2.2/MSW98/Python2.0.
Trying to use 2.3.1 I've some difficulties, if I recreate dialogs with a
grid inside.
I've menue for changing the display language (german/english/...), so I
.Destroy()
all the old windows
(splitter/tree,notebook/scrolledwindow/controls,grid(s))
and recreate them new.
That's running well with 2.2.2 but with 2.3.1 after several
menue-actions (10 or more)
the background greys and the controls and grids are crippled.

Please send a sample.

···

--
Robin Dunn
Software Architect
Sliceware, Inc.
Robin.Dunn@Sliceware.com

Hi Udo,

This sounds exactly like windows resource problems to me.

Open up your resource meter from Programs->Accessories->System tools.

Check if you have any code that create objects (that contain GDI
resources like bitmaps, menus, controls, etc.) in a loop that
might not be freed.

Does wxPython HYBRID version report leaked objects when your program
closes?

Windows 9x and friends are really pathetic in this respect. If a
program crashes it's resources aren't necessarily released. Usually
takes a reboot to get all the resources back.

Udo Floegel wrote:

···

I still use wxPython2.2.2/MSW98/Python2.0.
Trying to use 2.3.1 I've some difficulties, if I recreate dialogs with a
grid inside.
I've menue for changing the display language (german/english/...), so I
.Destroy()
all the old windows
(splitter/tree,notebook/scrolledwindow/controls,grid(s))
and recreate them new.
That's running well with 2.2.2 but with 2.3.1 after several
menue-actions (10 or more)
the background greys and the controls and grids are crippled. I can
close my
program and call it again, than I don't need any trials it's bad from
the beginning,
also some other MSW-applications have the same "decorations" (I've to
reboot).
The result of my trials is that it must displayed a grid, than it
happens, but sure I'm not.

Thanks, Udo

_______________________________________________
wxpython-users mailing list
wxpython-users@lists.wxwindows.org
http://lists.wxwindows.org/mailman/listinfo/wxpython-users

--
Riaan Booysen
___________________________________________________
Boa Constructor - RAD GUI building IDE for wxPython
     http://boa-constructor.sourceforge.net

Riaan Booysen wrote:

This sounds exactly like windows resource problems to me.

Open up your resource meter from Programs->Accessories->System tools.
Check if you have any code that create objects (that contain GDI
resources like bitmaps, menus, controls, etc.) in a loop that
might not be freed.

GDI-resource-display:
with wx2.2.2: it goes from 85% after 26 dialog-recreations to 80%
              and after closing back to the value before calling
with wx2.3.1: from 85% after 13 recreations to 69% and the next makes
              it grey, after closing it rests there, it rests at the
              last respective value also with fewer count of trials
              and a higher percentage.
Why with each recreation it's decreasing ?
In this case the recreation was done per setting the holders with
the reference to the new dialogelements, no extra .Destroy() before.

Does wxPython HYBRID version report leaked objects when your program
closes?

running: 3x assert ..\common\string.cpp(1944)
        (3 notebookpages with a grid inside)
The closing-report, and what is to do ? The program was called fom
__main__, but it can be called too from a other one.

C:\c3>python EAW.py -com COM1 -adr 1 -bd 19200 -rel DSRZE2 -short rze
-struct 7000
10:12:42: There were memory leaks.
10:12:42: ----- Memory dump -----
10:12:42: wxHtmlHelpController at $1E70E18, size 68
10:12:42: wxHtmlHelpController at $1E71E08, size 68
10:12:42: wxObject at $1E728C8, size 28
10:12:42: wxObject at $1E72478, size 28
10:12:42: wxFont at $1E75148, size 12
10:12:42: wxFont at $1E6A518, size 12
10:12:42: wxFont at $1E69CE8, size 12
10:12:42:
10:12:42:
10:12:42: ----- Memory statistics -----
10:12:42: 3 objects of class wxFont, total size 36
10:12:42: 2 objects of class wxObject, total size 56
10:12:42: 2 objects of class wxHtmlHelpController, total size 136
10:12:42:
10:12:42: Number of object items: 7
10:12:42: Number of non-object items: 0
10:12:42: Total allocated size: 228

regards, Udo