[wxPython-users] Splash screen refresh issue

[David Poundall]

> -----Original Message-----
> From: Robin Dunn [mailto:robin at alldunn.com]
> Sent: 03 January 2008 17:51
> To: wxPython-users at lists.wxwidgets.org
> Subject: Re: [wxPython-users] Splash screen refresh issue
> 
> David Poundall wrote:
> >>> Robin Wrote:
> >>> #1 rule in GUI programming (well, 2nd one, after "Choose wxPython"
> >>> <wink!>) is  to never block the GUI thread.  If you stop the flow of
> >>> control from getting into or getting back to the MainLoop then events
> >>> (like the paint events for the splash screen) will not be delivered to
> >>> their handlers.
> >>>
> >>> See http://wiki.wxpython.org/LongRunningTasks
> >>>
> >> David Wrote:
> >> Clean forgot about that one Robin, thanks for the polite poke.
> >>
> >
> > On a final note to do with splash screens, the difference between these
> two
> > splash screen codes ...
> >
> [...]
> > ... appears to be that the second code has an OnPaint.
> 
> So does the first class, it just happens to be in the base class instead
> of yours.
> 

I could see that the sw.Splashscreen will be subclassed from a wx.Frame at
some point, so I am not surprised to here you say that.  So... it must be
that either :

1. The Wx.Frame code is doing something that the wx.Splashscreen isn't
causing processing to be released before it should be ie. before the frame
is fully drawn.
 
2. Or ... you must be using the wx.Magic class somewhere in the
wx.Splashscreen code.  Problem is I can't seem to find much documentation on
wx.Magic at all ;-)

Or a combination of the 2.

Thank you for responding on this Robin.  Time for me to start to arm wrestle
with MySQL for a while now I think.

- David 

No virus found in this outgoing message.
Checked by AVG Free Edition. 
Version: 7.5.516 / Virus Database: 269.17.13/1207 - Release Date: 02/01/2008
11:29