summaryrefslogtreecommitdiff
path: root/gtk/gtkstyle.h
diff options
context:
space:
mode:
authorHavoc Pennington <hp@pobox.com>2010-09-11 19:25:57 -0400
committerHavoc Pennington <hp@pobox.com>2010-09-12 21:47:09 -0400
commitb3079c0d18b176bb5e939bf3fefdc2f5852e0a56 (patch)
treef6d4ae152b88bc23ab5321964b1b2a231b03a4c4 /gtk/gtkstyle.h
parent7e520d908aab0cd6d31fbabebf54a6fe349e5967 (diff)
downloadgtk+-b3079c0d18b176bb5e939bf3fefdc2f5852e0a56.tar.gz
Use gint16 for GtkBorder
32K of border ought to be enough for any pixel dimensions. At least until screens are so huge we start using doubles. This saves a nice 64 bits of space when we have a GtkBorder stored somewhere. Signed integers are used to avoid surprising unsigned math issues. Just search GTK's whole git log from inception for "unsigned" if you want to find any number of commits fixing signed/unsigned bugs. https://bugzilla.gnome.org/show_bug.cgi?id=629387
Diffstat (limited to 'gtk/gtkstyle.h')
-rw-r--r--gtk/gtkstyle.h8
1 files changed, 4 insertions, 4 deletions
diff --git a/gtk/gtkstyle.h b/gtk/gtkstyle.h
index f3312baae1..b425aa6d26 100644
--- a/gtk/gtkstyle.h
+++ b/gtk/gtkstyle.h
@@ -416,10 +416,10 @@ struct _GtkStyleClass
*/
struct _GtkBorder
{
- gint left;
- gint right;
- gint top;
- gint bottom;
+ gint16 left;
+ gint16 right;
+ gint16 top;
+ gint16 bottom;
};
GType gtk_style_get_type (void) G_GNUC_CONST;