No, it means exactly the opposite.Does that mean that the QIcon keeps hold of the QPixmap?
If the QIcon had its own deep copy, it wouldn't need the external pixmap object to stay alive.
Not darf at all, would be better if more people would think that far to ask it.If I do create it on the heap, who's reponsible for deleting it? Apologies if this seems like a daft question...
The answer depends on how you allocate your pixmap.
If you give it a QObject parent, you don't have to worry about destruction, the parent will.
If its parent-less, you will have to take care of deleting it.
Bookmarks