Den 2022-08-01 kl. 18:01, skrev Baldvin Kovacs:
1.
https://developer-old.gnome.org/gtkmm-tutorial/stable/chapter-customwidgets.html.en
developer-old.gnome.org is not updated any more. The latest version of
the gtkmm tutorial is stored at
Kjell Ahlstedt ezt írta (időpont: 2022. aug. 1.,
H, 11:05):
> Den 2022-07-31 kl. 00:37, skrev Baldvin Kovacs:
>
> I took a stab at it, PTAL. Another option is to not do this, but document
> in both the howtos, and the documentation
> of Gtk::Widget that container-like custom widgets are not
Den 2022-07-31 kl. 00:37, skrev Baldvin Kovacs:
I took a stab at it, PTAL. Another option is to not do this, but
document in both the howtos, and the documentation
of Gtk::Widget that container-like custom widgets are not supported.
Thx,
Baldvin
I have updated the custom container example in
Baldvin Kovacs ezt írta (időpont: 2022. júl.
30., Szo, 22:59):
> Sorry, I'll get on it now. It was part of my learning effort, and once
> I've understood everything, I went on with simply inheriting my widget from
> Box, so I forgot about this.
> Baldvin
>
> Kjell Ahlstedt ezt írta (időpont:
Sorry, I'll get on it now. It was part of my learning effort, and once I've
understood everything, I went on with simply inheriting my widget from Box,
so I forgot about this.
Baldvin
Kjell Ahlstedt ezt írta (időpont: 2022. júl. 30.,
Szo, 12:11):
> Den 2022-07-30 kl. 11:46, skrev Kjell
Den 2022-07-30 kl. 11:46, skrev Kjell Ahlstedt:
Den 2022-07-10 kl. 13:28, skrev Baldvin Kovacs:
I'll send a merge request with exposing signal_destroy, and another
small one to the documentation, to the custom widget section.
Baldvin
What has happened with the merge requests? I can easily
Den 2022-07-10 kl. 13:28, skrev Baldvin Kovacs:
I'll send a merge request with exposing signal_destroy, and another
small one to the documentation, to the custom widget section.
Baldvin
What has happened with the merge requests? I can easily add
_WRAP_SIGNAL(void destroy(), "destroy")
Kjell Ahlstedt ezt írta (időpont: 2022. júl. 10.,
V, 13:06):
> Den 2022-07-09 kl. 18:50, skrev Andrew Potter via gtkmm-list:
>
> Beyond exposing the destroy signal, another approach might be adding a
> virtual dispose method if there is some known problem with sigc++ at this
> point in the
Den 2022-07-09 kl. 18:50, skrev Andrew Potter via gtkmm-list:
Beyond exposing the destroy signal, another approach might be adding a
virtual dispose method if there is some known problem with sigc++ at
this point in the object lifecycle.
Adding a virtual method to an existing class breaks ABI.
On Fri, Jul 8, 2022 at 11:10 AM Baldvin Kovacs
wrote:
>
> The one I linked in the original email follows well the pattern I have:
> https://github.com/baldvin-kovacs/gtkmm-destroy-demo/blob/main/gtkmm-destroy-demo.cc
> . Now I added the #if to make it compile and run without the exposed
>
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:
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
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.
>>
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
14 matches
Mail list logo
