Weird initial screen behaviour

Dick Kniep wrote:

···

On Wednesday 18 February 2004 01:05, Robin Dunn schreef: > >>Dick Kniep wrote:

Hi list,

I have written about this problem before, but I still cannot figure out
what is happening. Included is a small sample that shows a part of the
problem (but not all). I am running Windows XP Professional with all
patches applied, wxPython2.4.2.4 and Python 2.3.3.

When I run this sample under Windows XP it flashes the correct screen and
then deletes the first two columns of the list, and also doesn't show the
second tab of the lower part of the screen. When I click in one of those
columns the specific line is displayed, the other lines stay blank. When
I click on one of the tabs, the screen is refreshed and displayed
correctly.

This is part of a bigger problem where in the "real" application only the
first tab on the top is shown, and nothing else, beside the menu's (that
DO work).

On Linux, there is no problem.
If anyone could help me, I would really appreciate it.

There seems to be some strange interaction happening between the
wxCLIP_CHILDREN style being used on the ClientenScrn class and its
parent notebook. Not sure why but removing either one of them works.

I have tried your suggestion, but it doesn't seem to work. Is there any chance that this is solved quickly? We need this program on Windows also, so I am kind of desparate....

Another thing to try is to use wxCallAfter to cause a function to be called after things have all been created and shown. Things to try in that funciton are to call Refresh on the listctrl, or perhaps sending an extra EVT_SIZE event to the splitter or notebook.

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

On Thursday 19 February 2004 20:33, Robin Dunn schreef:

Another thing to try is to use wxCallAfter to cause a function to be
called after things have all been created and shown. Things to try in
that funciton are to call Refresh on the listctrl, or perhaps sending an
extra EVT_SIZE event to the splitter or notebook.

Hi Robin,

I will try this this week, and let you know. Is this treated as a bug? Because
I really think it is.

Could it help if I tried to use a notebooksizer?

Cheers,
Dick Kniep

Dick Kniep wrote:

On Thursday 19 February 2004 20:33, Robin Dunn schreef:

Another thing to try is to use wxCallAfter to cause a function to be
called after things have all been created and shown. Things to try in
that funciton are to call Refresh on the listctrl, or perhaps sending an
extra EVT_SIZE event to the splitter or notebook.

Hi Robin,

I will try this this week, and let you know. Is this treated as a bug? Because I really think it is.

Yes, probably.

Could it help if I tried to use a notebooksizer?

No, it won't help with refreshing issues, just with sizing and layout of a notebook. You've already got that handled.

···

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

> On Thursday 19 February 2004 20:33, Robin Dunn schreef:
>>Another thing to try is to use wxCallAfter to cause a function to be
>>called after things have all been created and shown. Things to try in
>>that funciton are to call Refresh on the listctrl, or perhaps sending an
>>extra EVT_SIZE event to the splitter or notebook.
>
> Hi Robin,
>
> I will try this this week, and let you know. Is this treated as a bug?
> Because I really think it is.

Yes, probably.

I posted it as a bug on the wxWindows/wxPython Sourceforge page.

> Could it help if I tried to use a notebooksizer?

No, it won't help with refreshing issues, just with sizing and layout of
a notebook. You've already got that handled.

Any other alternatives? (I have tried the wxCallAfter....)

Cheers,
Dick

···

On Wednesday 25 February 2004 23:24, Robin Dunn schreef: > Dick Kniep wrote: