Re: [GnomeMeeting-devel-list] 1.00 Freeze

["Damien Sandras" <dsandras seconix com>]

Le 29/1/2004, "PUYDT Julien" <julien puydt laposte net> a écrit:

>On mer, 2004-01-28 at 21:01, Damien Sandras wrote:
>> > * why are gnomemeeting_threads_* calls needed? Is gdk broken?
>>
>> ??!? Why would GDK be broken?
>
>Well, if it needs to be protected against concurrent access from two
>threads, I consider it broken... If it doesn't, then why lock&unlock?
>

That's not new. I thought you knew this since a long time. GTK and GDK
are not thread-safe, so you always have to protect from concurrent
access. Callbacks are automatically protected though, but not timers and
idle functions or gconf notifiers.

Notice GConf is not thread-safe either. So you have to use gdk_threads_
to access GConf.

>> > * how should the class get the name of the file to open (ui-wise)?
>> I have to think about it.
>
>Eh, looking at the video devices page in the pref, I see there's already
>something there! So I don't really have to care about the ui... But more
>about how to do it clean and well.
>

Yes, we could get it from the GConf string. The code was already there,
but requires a redesign. However, I'm not sure getting things from
GConf inside that plugin is a good idea.

>Snark
>
>_______________________________________________
>Gnomemeeting-devel-list mailing list
>Gnomemeeting-devel-list gnome org
>http://mail.gnome.org/mailman/listinfo/gnomemeeting-devel-list