libhandy merge requestshttps://gitlab.gnome.org/GNOME/libhandy/-/merge_requests2021-02-16T08:30:06Zhttps://gitlab.gnome.org/GNOME/libhandy/-/merge_requests/637avatar: Allow loading custom avatar from GLoadableIcon2021-02-16T08:30:06ZJulian Sparberjulian@sparber.netavatar: Allow loading custom avatar from GLoadableIconSetting the GLoadableIcon allows use to handle loading, updating and resizing internally.
This is especially useful when using HdyAvatar in combination with libfolks
Vala example:
```
contact.bind_property("avatar",
...Setting the GLoadableIcon allows use to handle loading, updating and resizing internally.
This is especially useful when using HdyAvatar in combination with libfolks
Vala example:
```
contact.bind_property("avatar",
this.avatar,
"loadable-icon",
BindingFlags.SYNC_CREATE);
```
cc: @exalm
Todos:
- [x] Deprecate `set_image_func()` (I don't seam to do it correctly)
- [x] Add `hdy_avatar_draw_to_pixbuf_async ()`
- [x] Update docs to the new way of loading an avatar
- [x] Fix test1.1https://gitlab.gnome.org/GNOME/libhandy/-/merge_requests/663demo: Use style classes rather than label attributes2021-01-09T17:10:21ZAdrien Plazasdemo: Use style classes rather than label attributesThis covers what hasn't been converted to `HdyStatusPage` in https://gitlab.gnome.org/GNOME/libhandy/-/merge_requests/638.
WIP as it makes more sense to merge after https://gitlab.gnome.org/GNOME/libhandy/-/merge_requests/638, even if t...This covers what hasn't been converted to `HdyStatusPage` in https://gitlab.gnome.org/GNOME/libhandy/-/merge_requests/638.
WIP as it makes more sense to merge after https://gitlab.gnome.org/GNOME/libhandy/-/merge_requests/638, even if they are independent.1.1https://gitlab.gnome.org/GNOME/libhandy/-/merge_requests/664preferences-window: Use HdyStatusPage for the empty search2020-12-18T15:52:23ZAdrien Plazaspreferences-window: Use HdyStatusPage for the empty searchThis makes the code simpler and UIs look more cohesive.
~~WIP as it depends on https://gitlab.gnome.org/GNOME/libhandy/-/merge_requests/638.~~This makes the code simpler and UIs look more cohesive.
~~WIP as it depends on https://gitlab.gnome.org/GNOME/libhandy/-/merge_requests/638.~~1.1https://gitlab.gnome.org/GNOME/libhandy/-/merge_requests/678Refine preferences sizing2021-02-07T21:44:55ZAdrien PlazasRefine preferences sizingThis improves the spacing in preferences group and use CSS a bit more to implement sizing.This improves the spacing in preferences group and use CSS a bit more to implement sizing.1.1https://gitlab.gnome.org/GNOME/libhandy/-/merge_requests/679status-page: Hide title/description when they're empty or NULL2020-12-18T13:31:44ZAndrei Lișițăstatus-page: Hide title/description when they're empty or NULLFixes https://gitlab.gnome.org/GNOME/libhandy/-/issues/387Fixes https://gitlab.gnome.org/GNOME/libhandy/-/issues/3871.1https://gitlab.gnome.org/GNOME/libhandy/-/merge_requests/684flap: Properly calculate minimum and natural sizes2021-01-06T18:45:35ZAlice Mikhaylenkoflap: Properly calculate minimum and natural sizesCurrently, we always calculate minimum and natural size th esame way. This
technically works, but is incorrect semantically. For example, it means
that flap's natural size changes depending on whether it's currently
folded, while folding...Currently, we always calculate minimum and natural size th esame way. This
technically works, but is incorrect semantically. For example, it means
that flap's natural size changes depending on whether it's currently
folded, while folding state may change depending on the allocated size.
Instead, calculate natural size as follows:
* When the flap is always folded, do the same thing as berore
* When it's never folded, assume natural to be what the flap will be like
when fully revealed
* For the automatic policy, an important distinction is whether the flap is
locked or not. If it's not locked, we can safely assume the size when
unfolded and fully revealed as well, but if it is locked and the flap is
not revealed, we assume that to be the natural size, because the flap
will never be auto-revealed on resizeing, and unlike the never folded
state, revealing the flap will not cause a widget resize either.
Additionally, never account for the separator size for the flap's
orientation. When folded, the separator will end up completely offscreen,
and it's expected and supported situation.1.1https://gitlab.gnome.org/GNOME/libhandy/-/merge_requests/688keypad: Allow pasting and erasing text in the entry2021-01-07T09:29:54ZAlice Mikhaylenkokeypad: Allow pasting and erasing text in the entryStop assuming that input is going to be 1 char only, instead allow it if
all characters are valid. Take care to handle unicode correctly.
Fixes https://gitlab.gnome.org/GNOME/libhandy/-/issues/394Stop assuming that input is going to be 1 char only, instead allow it if
all characters are valid. Take care to handle unicode correctly.
Fixes https://gitlab.gnome.org/GNOME/libhandy/-/issues/3941.1https://gitlab.gnome.org/GNOME/libhandy/-/merge_requests/689test-combo-row: Check if property notify events are emitted correctly2021-01-04T08:38:50ZAndrei Lișițătest-combo-row: Check if property notify events are emitted correctly1.1https://gitlab.gnome.org/GNOME/libhandy/-/merge_requests/708stackable-box: Fix natural size calculation for deck2021-02-16T11:44:44ZAlice Mikhaylenkostackable-box: Fix natural size calculation for deckFixes https://gitlab.gnome.org/GNOME/libhandy/-/issues/404Fixes https://gitlab.gnome.org/GNOME/libhandy/-/issues/4041.1https://gitlab.gnome.org/GNOME/libhandy/-/merge_requests/713Follow-up tab fixes2021-02-16T08:30:06ZAlice MikhaylenkoFollow-up tab fixesSee individual commits.See individual commits.1.1