Re: gtk-devel-list Digest, Vol 157, Issue 3
- Date: Wed, 3 May 2017 13:56:43 +0100
- From: Daniel Boles <dboles.src@xxxxxxxxx>
- Subject: Re: gtk-devel-list Digest, Vol 157, Issue 3
On 3 May 2017 at 13:00, <gtk-devel-list-request@xxxxxxxxx> wrote:
From: Murray Cumming <murrayc@xxxxxxxxxxx>
To: Timm B?der <mail@xxxxxxxxxxx>
Cc: gtk-devel-list <gtk-devel-list@xxxxxxxxx>
Subject: Re: gtk4: gtk_box_pack_start()/end() porting
Content-Type: text/plain; charset="UTF-8"
On Fri, 2017-04-28 at 17:50 +0200, Murray Cumming wrote:
> On Fri, 2017-04-28 at 17:20 +0200, Timm B?der wrote:
> > I've added notes about the fill and expand child properties to the
> > migration guide:
> > https://git.gnome.org/browse/
> > d5
> > fdab685218bbac29
> Thanks. I guess it's that last part about hexpand/vexpand affecting
> parent widgets too that explains what I've seen so far. So there is
> really no simple mapping from the old API to the new API. Porting is
> going to be rather awkward.
Have some container widgets changed, or lost, some default
spacing/padding/margins too? For instance, it looks like GtkActionBar
used to have some hard-coded spacing between its child widgets (added
via gtk_action_bar_pack_start()), but not with gtk4.
Based on some commits I remember seeing, I think the new policy is that widgets should not enforce such properties. Which, IMO, is a good thing, though again potentially a pain for porting.
_______________________________________________ gtk-devel-list mailing list gtk-devel-list@xxxxxxxxx https://mail.gnome.org/mailman/listinfo/gtk-devel-list