Re: [java-gnome-hackers] Idle coverage

[Guillaume M. <res...@gm...>]

2012/8/25 Andrew Cowie <an...@op...>:
> Guillaume uncovered a bug;
That's what I do :)

> Anyway, if you're working from another thread and need to update your
> GTK widgets, you must do so from within the main loop. To get there, you
> add an idle handler which will get a callback at some future point. See
> http://java-gnome.sourceforge.net/doc/api/4.1/org/gnome/glib/Glib.html#idleAdd(org.gnome.glib.Handler)
>
> It'd really be rather nice if the people with experience with the
> toolkit could have a look at this implementation and tell me if it's
> done right. In particular, have a look at:
> http://research.operationaldynamics.com/bzr/java-gnome/mainline/src/bindings/org/gnome/glib/GMain.c
It looks fine to me. I'll test this on a real world application.

> Given the massive capability loss this represents, I rather think we
> should remove this as 4.2.0; should I mark it deprecated in 4.1.2?
I guess that it should be marked as deprecated and remove in 4.2.0.
Since GDK/GTK does not take care of this anymore we should get rid of
this in a next new major release.

> I've also dramatically updated the documentation around the Application
> coverage. I _think_ I've got it all squared away now, but perhaps you'll
> comment.
> http://java-gnome.sourceforge.net/doc/api/4.1/org/gnome/gtk/Application.html
Nothing to say, great documentation.

-- 
Guillaume Mazoyer - http://respawner.fr/