Re: Unparenting from GtkWidget "destroy"

Andrew Potter ezt írta (időpont: 2022. júl. 8., P, 19:45): > > On Fri, Jul 8, 2022 at 9:26 AM Baldvin Kovacs > wrote: > >> Andrew Potter ezt írta (időpont: 2022. júl. 8., P, >> 17:30): >> >>> >>> >>> On Fri, Jul 8, 2022, 4:01 AM Baldvin Kovacs via gtkmm-list < >>> gtkmm-list@gnome.org> wrote: >

Re: Unparenting from GtkWidget "destroy"

On Fri, Jul 8, 2022 at 9:26 AM Baldvin Kovacs wrote: > Andrew Potter ezt írta (időpont: 2022. júl. 8., P, > 17:30): > >> >> >> On Fri, Jul 8, 2022, 4:01 AM Baldvin Kovacs via gtkmm-list < >> gtkmm-list@gnome.org> wrote: >> >>> >>> 2. Expose the destroy signal handler, and document that one needs

Re: Unparenting from GtkWidget "destroy"

Andrew Potter ezt írta (időpont: 2022. júl. 8., P, 17:30): > > > On Fri, Jul 8, 2022, 4:01 AM Baldvin Kovacs via gtkmm-list < > gtkmm-list@gnome.org> wrote: > >> >> 2. Expose the destroy signal handler, and document that one needs to >> unparent children both from that, and in the destructor. >>

Re: Unparenting from GtkWidget "destroy"

On Fri, Jul 8, 2022, 4:01 AM Baldvin Kovacs via gtkmm-list < gtkmm-list@gnome.org> wrote: > > 2. Expose the destroy signal handler, and document that one needs to > unparent children both from that, and in the destructor. > Is this a new warning? My initial thought is this should be a feature of

Unparenting from GtkWidget "destroy"

Hello, I found that currently it is not possible to implement a Gtk::Widget descendant that properly unparents its children in case it is used in managed mode. gtk_widget_finalize will complain with g_warning ("Finalizing %s %p, but it still has children left:", gtk_widget_get_name (widget), widg