Re: Clarification of GTK/GDK locking pre GTK 4.0

From: Paul Davis <paul linuxaudiosystems com>
To: Emmanuele Bassi <ebassi gmail com>
Cc: Yehouda Harpaz <yeh lispworks com>, gtk-list gnome org
Subject: Re: Clarification of GTK/GDK locking pre GTK 4.0
Date: Fri, 14 Sep 2012 10:43:45 -0400

On Fri, Sep 14, 2012 at 6:38 AM, Emmanuele Bassi <ebassi gmail com> wrote:

the API that has been deprecated is, anyway, related to *acquiring*
and *releasing* the lock from outside of GDK; the gdk_threads_add_*
API has not been deprecated, and it's considered the only way to
schedule operations from within the GDK lock.

this is wierd, because i could swear that its been said many times that g_idle_add() is the right API to use for such things. what am i missing?

Follow-Ups:
- Re: Clarification of GTK/GDK locking pre GTK 4.0
  - From: Emmanuele Bassi

References:
- Clarification of GTK/GDK locking pre GTK 4.0
  - From: Yehouda Harpaz
- Re: Clarification of GTK/GDK locking pre GTK 4.0
  - From: Emmanuele Bassi

[Date Prev][Date Next] [Thread Prev][Thread Next] [Thread Index] [Date Index] [Author Index]