I'm trying to get my head around GTK+ 3.0's new 'Height-for-width
Geometry Management'. Sorry if I'm missing it in the documentation
somewhere, but what exactly is the definition of a widget's natural
width or height?
___
gtk-devel-list mailing list
gtk-d
On Sun, Sep 25, 2011 at 5:36 PM, Matthew Bucknall
wrote:
> I'm trying to get my head around GTK+ 3.0's new 'Height-for-width
> Geometry Management'. Sorry if I'm missing it in the documentation
> somewhere, but what exactly is the definition of a widget's natural
> width or height?
its pretty sim
On 25 September 2011 23:07, Paul Davis wrote:
> On Sun, Sep 25, 2011 at 5:36 PM, Matthew Bucknall
> wrote:
>> I'm trying to get my head around GTK+ 3.0's new 'Height-for-width
>> Geometry Management'. Sorry if I'm missing it in the documentation
>> somewhere, but what exactly is the definition of
On Sun, Sep 25, 2011 at 6:20 PM, Matthew Bucknall
wrote:
> What I'm not clear on is the meaning of the 'natural' arguments in
> calls to gtk_widget_get_preferred_height () and
> gtk_widget_get_preferred_width ().
>
> Are the natural sizes just some sort hint to containers which may
> result in mo
On Sun, 2011-09-25 at 18:23 -0400, Paul Davis wrote:
> On Sun, Sep 25, 2011 at 6:20 PM, Matthew Bucknall
> wrote:
>
> > What I'm not clear on is the meaning of the 'natural' arguments in
> > calls to gtk_widget_get_preferred_height () and
> > gtk_widget_get_preferred_width ().
> >
> > Are the nat
GTK+ 3.2.0 is now available for download at:
http://download.gnome.org/sources/gtk+/3.2/
ftp://ftp.gtk.org/pub/gtk/3.2/
bce3c1a9be6afd7552c795268656d8fdd09c299765a7faaf5a76498bb82ed44c gtk
+-3.2.0.tar.xz
b285074ffefb4ff4364f6dd50fe68c7e85b11293e0c1dd3bdeac56052344dadb gtk
+-3.2.0.tar.bz2
Wh
https://bugzilla.gnome.org/show_bug.cgi?id=660095
Its small, it doesn't affect anything except Windows and it fixes an actual
build problem if your environment does have dirent.h. Thank you.
Kean
___
gtk-devel-list mailing list
gtk-devel-list@gnome.o
In at least gstdio.c, possibly other places (I am still looking) there is a
lot of code to use the "wide" versions of various functions like stat,
because it is assumed that the input argument is UTF-8 and the CRT doesn't
support UTF-8 directly but rather Microsoft's own multibyte character set