Hey,
with the latest commits[1] I have added reftests to GTK. Reftests are
my approach at getting layout and rendering behavior of gtk tested.
I've added a bunch of tests already for the things I have fixed and
will continue to add tests for bugs I fix. For what the test runner
does, see the
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
On 05/03/11 16:01, Benjamin Otte wrote:
(Pango doesn't ellipsize every row, only the
last one. Bad Pango - and Behdad hasn't even applied my patch for
this, I need to poke him again as I've just committed that test,
ooops.)
You see. No Pango test suite means little confidence that an
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
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
2011/5/3 Pavol Klačanský pa...@klacansky.com:
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
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
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 :
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.
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
On Tue, 3 May 2011 22:06:02 +0200, Tadej Borovšak tadeb...@gmail.com
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
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
On Tue, 3 May 2011 22:50:38 +0200, Tadej Borovšak tadeb...@gmail.com
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
13 matches
Mail list logo