Hi Chris,
Thanks for your great help!!!
I finally find out why the deadlock always occurs after 5 minutes.
My applications has a function the autosave the document every X minute,
and I use the g_timeout_add_seconds with callback to handle it. However
the callback contains a line 'while (gtk_even
Inside my gtk application, I'd like to get (i.e. discover) the name of the
current theme,which I believe is the "gtk-theme-name" property of the
current window's GtkSettings.
I see how to retrieve the GtkSettings object , using
gtk_settings_get_default () or gtk_settings_get_for_screen
On Sun, 6 Mar 2011 16:03:43 +
Chris Vine wrote:
> On Sun, 6 Mar 2011 10:57:24 +0800
> Wei-Ning Huang wrote:
[snip]
> > I'm starting to think it's the bug of gtk+, or perhaps the
kernel?
> > btw, I'm using Arch Linux with Kernel 2.6.37(autogroup patched),
> > Gtk+ 2.22.
> >
> > SI once suspec
On Sun, 6 Mar 2011 10:57:24 +0800
Wei-Ning Huang wrote:
> Thanks Chris. I tried to remove any function call in the
> compile_thread, i.e:
>
> // Thread function
> // It is signaled to wake up for every 1 second
> gpointer motion_compile_thread(gpointer data) {
> ...
>while (TRUE) {
> if
Hi Allin,
I don't think it was the grace of god in my old makefiles. It was an
older version of gcc on my hard drive. Thank you for all your help.
Craig Bakalian
On Sat, 2011-03-05 at 21:36 -0500, Allin Cottrell wrote:
> On Sat, 5 Mar 2011, Craig Bakalian wrote:
>
> > Well call me a frog. I
