Doc: Bring QSizeF/QPointF::isNull() documentation up to date

Since Qt 5.0 (commit 09dd19df) sign is ignored when testing
whether a QPointF or QSizeF is null.

This updates the documentation accordingly.

Change-Id: I3de1c748f3caa63b8bd8990006de5ba572eac83e
Task-number: QTBUG-45669
Reviewed-by: Mitch Curtis <mitch.curtis@digia.com>
Reviewed-by: Venugopal Shivashankar <venugopal.shivashankar@digia.com>
This commit is contained in:
Topi Reinio 2015-04-17 14:32:02 +02:00 committed by Topi Reiniö
parent 21c90bcc98
commit b71535a923
2 changed files with 4 additions and 12 deletions

View File

@ -528,12 +528,8 @@ QDebug operator<<(QDebug dbg, const QPointF &p)
/*!
\fn bool QPointF::isNull() const
Returns \c true if both the x and y coordinates are set to +0.0;
otherwise returns \c false.
\note Since this function treats +0.0 and -0.0 differently, points
with zero-valued coordinates where either or both values have a
negative sign are not defined to be null points.
Returns \c true if both the x and y coordinates are set to 0.0 (ignoring
the sign); otherwise returns \c false.
*/

View File

@ -517,12 +517,8 @@ QDebug operator<<(QDebug dbg, const QSize &s)
/*!
\fn bool QSizeF::isNull() const
Returns \c true if both the width and height are +0.0; otherwise returns
false.
\note Since this function treats +0.0 and -0.0 differently, sizes with
zero width and height where either or both values have a negative
sign are not defined to be null sizes.
Returns \c true if both the width and height are 0.0 (ignoring the sign);
otherwise returns \c false.
\sa isValid(), isEmpty()
*/