exception from _gtk_quartz_...
663543 Huge memory leak while using MS-Windows theme (gtk-demo)
663605 Fix event->state of many event types on quartz
November 10, 2011
Alexander Larsson
___
gtk-app-devel-list mailing list
gtk-app-devel-list@gnome.o
On Tue, 2008-12-30 at 21:47 -0500, Yu Feng wrote:
> Dear Devels:
>
> I am having troubles because the GMutex used gdk_threads_enter/leave can
> be non-recursive.
>
> I have a piece of code (g_module_check_init) to either be called from an
> event dispatched by GDK(if the module is loaded via GtkS
On Sat, 2008-12-27 at 15:19 -0500, David Zeuthen wrote:
> GFuture *future;
> future = g_future_get (foo->pending_call);
> g_object_set_data (future, "other-stuff", other_stuff, g_object_unref);
>
> and the GFuture object would be unreffed when the pending call is
> finished.
I'd like to avoid
On Sat, 2008-12-27 at 04:21 -0500, Freddie Unpenstein wrote:
> This is a side-topic, raised by developments in handling DBus, but
> something I feel is worth asking... Is there any mechanism for making
> working with asynchronous stuff easier?
>
> Quite often I've had a situation where I've needed
