Re: [Deskbar] Att. async module loaders: Handy test module

[Joao Inacio <jcinacio gmail com>]

On 10/12/05, Raphael Slinckx <raphael slinckx net> wrote:
> On Wed, 2005-10-12 at 15:48 +0200, Mikkel Kamstrup Erlandsen wrote:
> > Good catch! We generally have to make sure any gtk stuff called from
> > initialize () is surrounded by gtk.threads_{enter,leave}... I don't know
> > if this is done...
> >
> > When we implement async handlers at some point writers of such handlers
> > should also note that any gtk interaction should be surrounded by
> > gtk.threads_{enter,leave}.
> >
> > I'll pu this in AsyncHandler __doc__-strings.
> >
> > Cheers
> > Mikkel
> >
> That was probably the cause of the Async Xlib reply.
>
> Concerning this, couldn't we surround the module.initialize() with
> threads enter/leave in the module_loader.py ? Or would that render
> threads useless ?
>
> By the way, the network places isn't the only one using gconf or gtk
> methods while called in a thread, i think mozilla and epiphany have
> gconf usage in global scope to retreive the browser preference. Must
> these also be placed in threads ?
>
>
> I hate threads.
> Raf
>

i'm guessing that in those handlers the gconf usage may be safe
(begining of the module), but the gtk pixbuf functions may be another
story...

--
João Inácio
jcinacio gmail com