There's one thing I've never quite understood: the correct
mechanism for destroying a gtk widget that is never parented or
shown.
The context is that I'm creating a temporary widget with
gtk_label_new(), just for the purpose of getting hold of its
PangoContext so I can figure something out about
On Thu, May 05, 2011 at 12:46:14AM +0530, pushparaj muthu wrote:
Iam trying to cross compile glib package for arm process by executing the
following command.
./configure --prefix =/home/glib/install --host=linux-arm --build=i686
--cache-file=arm_cache.conf
Note that --prefix specifies
Hi Benjamin,
On May 3, 2011, at 10:01 PM, Benjamin Otte wrote:
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
Charlie, I think that you forgot to send this to the mailing list.
On 2011-05-04 11:05, Charlie De charlieco...@yahoo.com wrote:
Well, I'm stunned, this is depressing!
What hurt or damage would it have done to have left the widget in? None
whatsoever. It leaves me wondering if you guys know
On 05/05/11 04:18, Kristian Rietveld wrote:
g_assert (allocation.y == rect.y + ((rect.height - allocation.height)
/ 2));
The output of this failed assertion is not really nice to the eyes. It would
be nice if the assertion macros could be improved to also accept a
human-readable
As an update: http://blogs.gnome.org/otte/2011/05/05/reftests/ has a
tutorial for writing reftests. I put it in my blog as it's nicer to
layout things there, I didn't want to send large GIF attachments via
email and it's reasonably easy for me to show it to anyone in the
future if I want them to
On Thu, May 5, 2011 at 10:18 AM, Kristian Rietveld k...@gtk.org wrote:
As we've already discussed on IRC some time ago, I would really like to see
all
GTK+ unit tests in one single place, instead of in several different places
in the
source code. We really need people to run the unit tests
