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

doc: Remove obsolete note for QWidget::paintEvent()

Browse Source 
qt_x11_set_global_double_buffer() is dead code since Qt 5.

Change-Id: Ie9a33b6f03dc2e39f12bc790292bb0d227f05c44
Reviewed-by: Tor Arne Vestbø <tor.arne.vestbo@qt.io>
This commit is contained in:
Alexander Volkov 2016-11-08 15:54:43 +03:00
parent 2265fbe7c1
commit 1c08046565
2 changed files with 0 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
src/widgets/doc/snippets/code/src_gui_kernel_qwidget.cpp
View File

@ -127,11 +127,3 @@ setUpdatesEnabled(false);
bigVisualChanges(); bigVisualChanges();
setUpdatesEnabled(true); setUpdatesEnabled(true);
//! [13] //! [13]
//! [14]
...
extern void qt_x11_set_global_double_buffer(bool);
qt_x11_set_global_double_buffer(false);
...
//! [14]

5
src/widgets/kernel/qwidget.cpp
View File

@ -9597,11 +9597,6 @@ void QWidget::leaveEvent(QEvent *)
Since Qt 4.0, QWidget automatically double-buffers its painting, so there Since Qt 4.0, QWidget automatically double-buffers its painting, so there
is no need to write double-buffering code in paintEvent() to avoid flicker. is no need to write double-buffering code in paintEvent() to avoid flicker.
\b{Note for the X11 platform}: It is possible to toggle global double
buffering by calling \c qt_x11_set_global_double_buffer(). For example,
\snippet code/src_gui_kernel_qwidget.cpp 14
\note Generally, you should refrain from calling update() or repaint() \note Generally, you should refrain from calling update() or repaint()
\b{inside} a paintEvent(). For example, calling update() or repaint() on \b{inside} a paintEvent(). For example, calling update() or repaint() on
children inside a paintevent() results in undefined behavior; the child may children inside a paintevent() results in undefined behavior; the child may