wxPython 2.5.2.2p.20040619 on win98

Jean-Michel_Fauth · June 21, 2004, 1:51pm

win98, Py 2.3.4, wxPython 2.5.2.2p.20040619

- Demo / Custom Controls / ColourSelect
When a button receives a new colour, it seems only the newly exposed region
(region that was hidden by the colour selector) of that button is refreshed.

- Demo / More Windows/Controls / DynamicSashWindow

From the log window,

Running demo DynamicSashWindow.py...
Debug: ..\..\include\wx/msw/private.h(297): 'GetWindowRect' failed with error 0x00000000 (l'opération s'est terminée.).
Debug: ..\..\include\wx/msw/private.h(297): 'GetWindowRect' failed with error 0x00000000 (l'opération s'est terminée.).
Debug: ..\..\include\wx/msw/private.h(297): 'GetWindowRect' failed with error 0x00000000 (l'opération s'est terminée.).
Debug: ..\..\src\msw\window.cpp(1506): 'MoveWindow' failed with error 0x00000000 (l'opération s'est terminée.).
Debug: ..\..\include\wx/msw/private.h(297): 'GetWindowRect' failed with error 0x00000000 (l'opération s'est terminée.).
Debug: ..\..\include\wx/msw/private.h(297): 'GetWindowRect' failed with error 0x00000000 (l'opération s'est terminée.).
Debug: ..\..\include\wx/msw/private.h(297): 'GetWindowRect' failed with error 0x00000000 (l'opération s'est terminée.).
Debug: ..\..\src\msw\window.cpp(1506): 'MoveWindow' failed with error 0x00000000 (l'opération s'est terminée.).

- Demo / More Windows/Controls / Time Ctrl
The text ctrls have "strange" sizes. See remark below (***)

- Demo / Windows layout / Sizers
As said in a previous post, on my win platform, I also see some black spaces
(lines with a 1-2 pixels width), between ctrls, where no space is expected.

- Demo window
It does not display the "mondrian" icon.

- From my apps / Strange behaviour of the wx.TextCtrl control
(***)
In something like:

self.txt = wx.TextCtrl(self, 3001, 'text control', (10, 100), (300, 30), wx.ST_NO_AUTORESIZE)
self.txt.SetFont(wx.Font(10, wx.MODERN, wx.NORMAL, wx.NORMAL, False))

the size of the ctrl is not set correctly. It always presents a fixed size of
approximatively (100, 25). When removing self.txt.SetFont(), everything is ok.
This is probably what happens in the Time Ctrl issue, the used fonts are
monospaced fonts. The masked.TextCtrl using a monospace font by
default, present the same bug.

- fixdc.py has done its job very well.

- I will probably not have the time to test all the beta releases, as I have done
with wxPython 2.5.1.5

Jean-Michel Fauth, Switzerland

Robin · June 21, 2004, 6:07pm

Jean-Michel Fauth wrote:

win98, Py 2.3.4, wxPython 2.5.2.2p.20040619

- Demo / Custom Controls / ColourSelect
When a button receives a new colour, it seems only the newly exposed region
(region that was hidden by the colour selector) of that button is refreshed.

Okay, should be an easy fix. Please do a little experimentation for me to see if adding a self.Refresh to the end of ColourSelect.SetColour works, or if perhaps doing it with a wx.CallAfter would be better.

- Demo / More Windows/Controls / DynamicSashWindow

From the log window,

Running demo DynamicSashWindow.py...
Debug: ..\..\include\wx/msw/private.h(297): 'GetWindowRect' failed with error 0x00000000 (l'opération s'est terminée.).
Debug: ..\..\src\msw\window.cpp(1506): 'MoveWindow' failed with error 0x00000000 (l'opération s'est terminée.).
Debug: ..\..\include\wx/msw/private.h(297): 'GetWindowRect' failed with error 0x00000000 (l'opération s'est terminée.).
Debug: ..\..\src\msw\window.cpp(1506): 'MoveWindow' failed with error 0x00000000 (l'opération s'est terminée.).

I'll try to duplicate this. Does it just show those messaages at the start or do they show up when resizing the sash windows?

- Demo / More Windows/Controls / Time Ctrl
The text ctrls have "strange" sizes. See remark below (***)

Probably related to the sizer issues that I mentioned in the other mail.

- Demo / Windows layout / Sizers
As said in a previous post, on my win platform, I also see some black spaces
(lines with a 1-2 pixels width), between ctrls, where no space is expected.

In this case it is the demo that is drawing the black lines. I changed the demo a while back to use just plain windows with a border to demonstrate layout because buttons can not be stretched like that on OSX.

- Demo window
It does not display the "mondrian" icon.

Yes, I noticed this too. I think I know the problem but havn't been able to verify and fix it yet due to other time constraints.

- From my apps / Strange behaviour of the wx.TextCtrl control
(***)
In something like:

self.txt = wx.TextCtrl(self, 3001, 'text control', (10, 100), (300, 30), wx.ST_NO_AUTORESIZE)
self.txt.SetFont(wx.Font(10, wx.MODERN, wx.NORMAL, wx.NORMAL, False))

the size of the ctrl is not set correctly. It always presents a fixed size of
approximatively (100, 25). When removing self.txt.SetFont(), everything is ok.
This is probably what happens in the Time Ctrl issue, the used fonts are
monospaced fonts. The masked.TextCtrl using a monospace font by
default, present the same bug.

Yes. See my other message.

- fixdc.py has done its job very well.

So code using fixdc and 2.5.1.5 needs no changes in 2.5.2.x? Excellent!

- I will probably not have the time to test all the beta releases, as I have done
with wxPython 2.5.1.5

Understood. Thanks in advance for whatever time you are able to put into it.

···

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

Robin · June 21, 2004, 6:26pm

Robin Dunn wrote:

Jean-Michel Fauth wrote:

- Demo / More Windows/Controls / DynamicSashWindow

From the log window,

Running demo DynamicSashWindow.py...
Debug: ..\..\include\wx/msw/private.h(297): 'GetWindowRect' failed with error 0x00000000 (l'opération s'est terminée.).
Debug: ..\..\include\wx/msw/private.h(297): 'GetWindowRect' failed with error 0x00000000 (l'opération s'est terminée.).
Debug: ..\..\include\wx/msw/private.h(297): 'GetWindowRect' failed with error 0x00000000 (l'opération s'est terminée.).
Debug: ..\..\src\msw\window.cpp(1506): 'MoveWindow' failed with error 0x00000000 (l'opération s'est terminée.).
Debug: ..\..\include\wx/msw/private.h(297): 'GetWindowRect' failed with error 0x00000000 (l'opération s'est terminée.).
Debug: ..\..\include\wx/msw/private.h(297): 'GetWindowRect' failed with error 0x00000000 (l'opération s'est terminée.).
Debug: ..\..\include\wx/msw/private.h(297): 'GetWindowRect' failed with error 0x00000000 (l'opération s'est terminée.).
Debug: ..\..\src\msw\window.cpp(1506): 'MoveWindow' failed with error 0x00000000 (l'opération s'est terminée.).

I'll try to duplicate this. Does it just show those messaages at the start or do they show up when resizing the sash windows?

Interesting... the error messages are "invalid window handle" for me, not "the operation is terminated" that gives it a totally different meaning! Looks like MS has a language translation problem. Anyway, I should be able to track this down once I get a little time.

···

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