Hey Rutger,
There is indeed something special about the ownership of the contents of a
menu item: eventually, the WStackedWidget will become owner of the
contents, but deferLoading may delay that until the menu item is actually
selected.
As to your original questions:
- contents stack is not owned by the menu (it can be shared between
different menus); it's owned by its parent instead.
- the menu owns the items
- a WMenu could indeed have a setContentsStack(), in fact, that would be
nicer than needing to pass it through the constructor
- similarly, a WMenuItem could also have a setContents()
For the latter two, feel free to file feature requests.
Regards,
koen
2013/6/13 Rutger ter Borg <rut...@terborg.net>
> On 2013-06-13 11:18, Dmitriy Igrishin wrote:
> >
> > It's parent object, since one contents stack can be shared accross
> > several WMenu's
> >
> > Who owns the contents? WStackedWidget, or WMenuItem, or?
> >
> > WMenuItem.
>
>
> Isn't the ownership of content transferred from WMenuItem to the
> WStackedWidget after loading?
>
> Rutger
>
>
>
>
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by Windows:
>
> Build for Windows Store.
>
> http://p.sf.net/sfu/windows-dev2dev
> _______________________________________________
> witty-interest mailing list
> witty-interest@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/witty-interest
>
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
witty-interest mailing list
witty-interest@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/witty-interest
