-
-
Notifications
You must be signed in to change notification settings - Fork 130
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Layout fixes #132
Layout fixes #132
Conversation
This commit virtually eliminates the need to use size hint constraints on a container. A child container now contributes constraints to its parent concerning its minimum and maximum size. This makes nested containers work the same with and without the shared_layout flag, provided constraints dont cross container boundaries.
This forces the dock item to expand when docked, irrespective of dock widget's constraints. This is the only really sane behavior since the dock area should alway be filled.
This updates the min/max size handling to only update the sizes of the widget when it's ancestor is not a container. When it has an ancestor container, the ancestor layout manager must be the ultimate authority on min/max size, not the toolkit.
the settings for size hint are no longer needed with the new layout updates.
this tweaks the size hint constraints and default constraints for the task dialogs so that they continue to have the same user-facing layout behavior when run against the new layout updates.
this adds support to the layout manager to support boundary constraints on a widget in addition to size hint constraints
provide reasoning for disable a container's size hint constraints by default.
this as a resist_width declaration to the nested container so that it behaves like the fluid example with respect to initial window size.
This updates the layout system to be more natural and consistent with respect to sizing of nested containers and dealing with intrinsic minimum and maximum sizes. This requires minor updates to user's layout code in certain cases where the previous implicit semantics of container layout no longer apply. All of the examples have been updated and tested to reflect the new semantics. In general, this allowed the removal of a lot of unnecessary code in the examples. |
No description provided.