thiago at kde.org
Mon Nov 27 07:26:44 GMT 2006
Charles Samuels wrote:
>KPageWidget has these ctors:
>public explicit KPageDialog( QWidget *parent = 0, Qt::WFlags flags = 0
> protected KPageDialog( KPageWidget *widget, QWidget *parent=0,
> Qt::WFlags=0 );
>When trying to call the first constructor with a KPageWidget, there is
> an ambiguity (This is a rare case).
Yeah, I guess. But you can workaround that by adding the third parameter.
Then there can be no ambiguity
It is a protected constructor anyways...
> KPageWidget *pageWidget() const;
>Should probably not be const. There should probably be a const and
> non-const version of that function.
Only if it has a different semantic. If the page widget isn't passed by
the constructor, is that function supposed to create it? Or is it
supposed to return 0?
If it's supposed to create it, the internal var could be mutable. If it's
supposed to return 0, it should remain const. But if you have both
semantics, then you should have two functions (one const and one
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
PGP/GPG: 0x6EF45358; fingerprint:
E067 918B B660 DBD1 105C 966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 189 bytes
Desc: not available
More information about the kde-core-devel