On Mon, 14 Sep 2009 18:02:25 -0400 (EDT)
Marshall Lake wrote:
> I'll be a son-of-a-gun. Removing the gdk_* calls fixed the problem.
> It's something I should have known.
The GDK global lock is difficult to use correctly. All GTK+ signal
callbacks are entered holding the lock (as is gtk_main(),
On Mon, 14 Sep 2009, Matthew Talbert wrote:
> In our GTK/GNOME application, our users would like the ability to use
> the program in a locale of their choice (out of the ~10 translations
> we have available) rather than detecting automatically which to use.
> (well, most users will be fine with a
> We've implemented this sort of thing -- a language selector that
> lets you choose between 13 supported languages -- in gretl,
> another GTK app. I'm not sure we're doing it in the best way, but
> it seems to work OK. It's definitely fiddly work. To see what we
> did, look at gretl_intl.c, line
2009/9/14 Daniel Leidert :
> In Debian the test suite of perl-gtk2 failed [1]. Examining the
> situation a bit further it seems, that even after setting a cursor, the
> reurned path from gtk_tree_view_get_cursor() is NULL. I tried to write s
> short program to reproduce this in C (attached). When I
