GNOME Bugzilla – Bug 584029
GtkVBox show horizontal
Last modified: 2010-05-03 22:13:41 UTC
Please describe the problem: Loading glade files (that were generated with glade3-3.4.5) using glade3-3.6.1, the GtkVBox show as horizontal. Steps to reproduce: 1. load an glade-3.4.5 generated file that has a VBox using glade3-3.6.1 2. look it display horizontally on the display 3. set the orientation to Vertical 4. save the file, look at the new ORIENTATION property Actual results: Complex UI look all scrambled and messed up Expected results: UI look as they are intended to Does this happen every time? Yes Other information: I'm not sure about this, but looking up for information, I found several widgets in GTK2 seems to have recently implemented GtkOrientable capability, that seems to default to GTK_ORIENTATION_HORIZONTAL: http://library.gnome.org/devel/gtk/unstable/gtk-Orientable.html In the old format of glade3-3.6.1, VBox did not have any orientation, so that was not save in the output xml. With the new version, that info is save in XMl. so I'm guessing because the property is not set in the old format, it takes the default, that's seems to be horizontal for all the widgets. Would be nice to get a default that matches the historic behaviour (Vertical for VBox, Horizontal for HBox, etc .. ) Not sure how many widgets are affected by that, but VBox is clearly one.
GtkVBox should explicitly set the default value of its orientation property to be VERTICAL at class_init time. Right now there is no other way to handle cases where the orientation is omitted (earlier versions of GTK+ did not have this property) - remember an omitted property in the builder file is the same thing as explicitly setting the property to its default value - at least this is the behavior we expect from Glade. Another approach would be to increment the builder format and expect an explicit listing of these properties (clunky and far from elegant). It would be really nice if we could consider any case of properties with misadvertized defaults as bugs... as I havent complained about this much in the past, I just spam those properties by always saving them, thats not going to work very well anymore as we can see.
> It would be really nice if we could consider any case > of properties with misadvertized defaults as bugs We do. I believe there may even be a bug about this. It is unfortunately relatively painful to fix, because changing default values of properties is not as easy as it should be in GObject.
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find. *** This bug has been marked as a duplicate of bug 587256 ***