1berry/qtbase
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Doc: Use nullptr in Signals & Slots

Browse Source 
Change-Id: I9b377e00ce177ae33972479bde11dd03061224d7
Reviewed-by: Paul Wicking <paul.wicking@qt.io>
This commit is contained in:
Kai Koehne 2019-03-12 16:04:10 +01:00
parent 6620f93a74
commit d5bb757987
2 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
src/corelib/doc/snippets/signalsandslots/lcdnumber.h
View File

@ -69,7 +69,7 @@ class LcdNumber : public QFrame
//! [6]
public:
//! [6] //! [7]
LcdNumber(QWidget *parent = 0);
LcdNumber(QWidget *parent = nullptr);
//! [7]
//! [8]

4
src/corelib/doc/src/objectmodel/signalsandslots.qdoc
View File

@ -330,7 +330,7 @@
arguments can have default values. Consider QObject::destroyed():
\code
void destroyed(QObject* = 0);
void destroyed(QObject* = nullptr);
\endcode
When a QObject is deleted, it emits this QObject::destroyed()
@ -339,7 +339,7 @@
A suitable slot signature might be:
\code
void objectDestroyed(QObject* obj = 0);
void objectDestroyed(QObject* obj = nullptr);
\endcode
To connect the signal to the slot, we use QObject::connect().