There are three kinds of constraints available: ordering, alignment and
dimension matching.
-Ordering constraints specify that the widgets should be placed next to other
-along X or Y axis. These operate on one axis at a time, so a widget could be
-"right of" another even if they are separated by hundreds of pixels vertically.
-The widgets will be separated by a spacing value, which is settable on a per-
-layout basis.
+Ordering constraints specify that the widgets should be placed next to each
+other along X or Y axis. These operate on one axis at a time, so a widget
+could be "right of" another even if they are separated by hundreds of pixels
+vertically. The widgets will be separated by a spacing value, which is
+settable on a per-layout basis.
Alignment constraints make the corresponding edges of two widgets be on the
same line. These are incompatible with ordering constraints, so only one or
undefined.
Since specifiyng constraints manually can be quite tedious, there are some
-derived Layout classes that implement common positioning patterns. See
-MixedRows and Grid.
+derived Layout classes that implement common positioning patterns. See Row,
+Column, MixedRows and Grid.
*/
class Layout
{
Layout &layout;
unsigned index;
Widget &widget;
+ Geometry autosize_geom;
Geometry geom;
std::list<Constraint> constraints;
Packing horiz_pack;
void autosize_changed();
};
+ enum SolveMode
+ {
+ UPDATE,
+ AUTOSIZE
+ };
+
class LinearProgram;
struct Pointers;
Sides margin;
unsigned row_spacing;
unsigned col_spacing;
+ Geometry autosize_geom;
static Pointers pointers[2];
void set_expand(Widget &, bool, bool);
void update();
+ void autosize();
protected:
- void find_constraint_group(Slot &, ConstraintType, std::set<Slot *> &);
- void sort_slots(std::list<Slot *> &, ConstraintType);
- void solve_constraints(int);
+ void solve_constraints(int, SolveMode);
};
} // namespace GLtk