GitLab

The default development branch is now `main`.
This commit only exists on `master` to point people
towards that.

window: Implement height-for-width for min size

See merge request !4183

fontchooser: Avoid setting variations needlessly

See merge request !4197

Setting variations to their default value causes
them to show up in the serialization of the font
description - a font description has no idea about
the default values, so can't filter them out.

Avoid that.

gesture: fix typo in docs

See merge request !4191

Benjamin Otte authored Nov 21, 2021 and Benjamin Otte committed Nov 21, 2021

Try to compute a min size that matches the current aspect ratio.

This means that when interactively resizing, we adapt the min size to
the current window area dynamically.

And that means that we always have a min size that is large enough, but
users can interactively cause it to be small-width x large-height,
large-width x small-width or anything inbetween.

window: Always clamp to max size

See merge request !4185

Unrealize ATContext on unroot

Closes #4421

See merge request !4136

Otherwise we can end up with a window that's too small in certain corner
cases after resizing.

... and not later.

Otherwise future calls to sizing fucntions will reuse an outdated cache
and compute wrong values.

When computing the window size, always try to clamp to the max size.
This will shrink a window down into a sane size if it was too big
before.

Fixes

Closes #4469

See merge request !4182

Store the enum nick, not the enum value. That way the file remains
human-readable.

Updated reftests to new expected output.

Testcase included

Fixes #4469

Previously, the code did not expand the size properly when a default
size was already set.

Reftest included.

Go back to using pango for glyph rendering

See merge request !4181

Using just cairo makes us lose hexboxes. So, until
we implement that ourselves, go back to using pango.

Printing the affected widget leads people to assume that it is to blame
for the error. However, the widget is the object the function is being
called on, not the caller. And the caller is doing it wrong.

Usually the caller is the parent widget, so we could print that one, but
it's only usually, it can be an issue propagating from a grandparent and
it doesn't tell you from where the function is called (allocation or
measuring), so you need a debugger anyway.

So don't put anything there instead.

x11: Trap error when getting CRTC info

See merge request !4169

This reverts commit 22847563.

a11y: return -1 if parent is NULL

See merge request !4179

Lots of sizing fixes

See merge request !4180

That consistency check is entirely outdated and just prints confusing
stuff.

This is a quickfix to avoid infinite runtime in nested boxes with
wrapped labels.

Test included

glib doesn't print debug messages by default anymore.

For shrinking children, we would not make sure of this and just throw
the current size at them.

When the stack is homogeneous in only one direction, the other direction
may produce min sizes to small for all children. Make sure to query at
least the min size for those.

that way, we can index them by orientation.

If halign=fill, force adjustment to height-for-width.
If valign=fill, force adjustment to width-for-height.
Otherwise look at request mode.

This way we don't try to adapt the filled dimension and only adjust
the one that is not set to fill.

This could lead to the wrong values being passed and computing invalid
sizes which would then lead to very unhappy code.

Test included.

It's not expensive to check it because we'll cache the dfault size
request anyway, and people do it wrong a lot.
As a bonus, don't do any return_if_fail(), just use the min size
instead.