Re: GtkNotebook with action on click of special tab

2011-05-03 Thread Bernhard Schuster
In the end it was as easy as replacing g_signal_connect with g_signal_connect_after Regards Bernhard ___ gtk-app-devel-list mailing list gtk-app-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/gtk-app-devel-list

Re: multiple tree views

2011-05-03 Thread Pavol Klačanský
V Nedeľa, 1. máj 2011 o 15:59 +0200, Colomban Wendling napísal(a): > Hi, > > Le 01/05/2011 15:03, Pavol Klačanský a écrit : > > Hi, I need in my about 5 and more treeviews. I created one using glade, > > but I don't know how can I use it multiple times, gtk says something > > like this > > > >> (

Re: multiple tree views

2011-05-03 Thread Bernhard Schuster
2011/5/3 Pavol Klačanský : > V Nedeľa, 1. máj 2011 o 15:59 +0200, Colomban Wendling napísal(a): >> Hi, >> >> Le 01/05/2011 15:03, Pavol Klačanský a écrit : >> > Hi, I need in my about 5 and more treeviews. I created one using glade, >> > but I don't know how can I use it multiple times, gtk says so

gtk+ 2 handling of X primary selection not optimal?

2011-05-03 Thread Andy Tai
Hi, with gtk+ 2.20 (as in Debian 6) if you use the left mouse button to select text, over standard gtk+ text widgets, such as the about box of a gtk+ program, it seems the X primary selection is updated every time you select one more character (as you drag). This is not the behavior when dragging

GSource object lifetime

2011-05-03 Thread Thomas Stover
trying to stop a memory leak (2.24.1 x86_64)... I'm repetitively calling g_idle_source_new(), g_source_set_callback(), g_source_attach() to get an idle callback to run in a separate thread. The callback in question always exits with FALSE. The docs for GSourceFunc() state: ... Returns :

Re: GSource object lifetime

2011-05-03 Thread Colomban Wendling
Le 03/05/2011 20:49, Thomas Stover a écrit : > trying to stop a memory leak (2.24.1 x86_64)... > > I'm repetitively calling g_idle_source_new(), g_source_set_callback(), > g_source_attach() to get an idle callback to run in a separate thread. The > callback in question always exits with FALSE.

Re: GSource object lifetime

2011-05-03 Thread Tadej Borovšak
Hi. > I'm repetitively calling g_idle_source_new(), g_source_set_callback(), > g_source_attach() to get an idle callback to run in a separate thread. The > callback in question always exits with FALSE. Do you call g_source_unref() after attaching it? Cheers, Tadej. -- Tadej Borovšak tadeboro.b

Re: GSource object lifetime

2011-05-03 Thread Thomas Stover
On Tue, 3 May 2011 22:06:02 +0200, Tadej Borovšak wrote: > Hi. > >> I'm repetitively calling g_idle_source_new(), g_source_set_callback(), >> g_source_attach() to get an idle callback to run in a separate thread. >> The >> callback in question always exits with FALSE. > > Do you call g_source_un

Re: GSource object lifetime

2011-05-03 Thread Tadej Borovšak
Hi. > That did help (I think I still have an unrelated leak). I think a few > things could be made more clear in the docs (I'm not 100% sure I'm correct > either): I must agree with you here. Docs are a bit scarce on this topic. But ... > -A newly created source (from g_idle_source_new() ) has a

Re: GSource object lifetime

2011-05-03 Thread Thomas Stover
On Tue, 3 May 2011 22:50:38 +0200, Tadej Borovšak wrote: > All that being said, maybe you could "cook up" a patch for API docs > with this info? I'm sure people would find it useful. > Is there a starting place to read how to go about doing that? -- www.thomasstover.com FLYNN LIVES!