From 713829b718e3842cec3266838d5692f754582de6 Mon Sep 17 00:00:00 2001 From: Paul Wicking Date: Tue, 5 Jan 2021 09:06:23 +0100 Subject: Doc: Link to correct location MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Reflow text to fit style while at it, to satisfy git clang-format. Pick-to: 6.0 5.15 Fixes: QTBUG-89709 Change-Id: Iab2bf09399adf2cb0f0219ab40978bb238825ae8 Reviewed-by: Topi Reiniö --- src/gui/math3d/qmatrix4x4.cpp | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'src/gui/math3d/qmatrix4x4.cpp') diff --git a/src/gui/math3d/qmatrix4x4.cpp b/src/gui/math3d/qmatrix4x4.cpp index 56a10b72c9..34f8a7d892 100644 --- a/src/gui/math3d/qmatrix4x4.cpp +++ b/src/gui/math3d/qmatrix4x4.cpp @@ -1902,15 +1902,15 @@ QMatrix4x4 QMatrix4x4::orthonormalInverse() const Normally the QMatrix4x4 class keeps track of this special type internally as operations are performed. However, if the matrix is modified - directly with {QLoggingCategory::operator()}{operator()()} or data(), then QMatrix4x4 will lose track of - the special type and will revert to the safest but least efficient - operations thereafter. + directly with \l {QMatrix4x4::}{operator()()} or data(), then + QMatrix4x4 will lose track of the special type and will revert to the + safest but least efficient operations thereafter. By calling optimize() after directly modifying the matrix, the programmer can force QMatrix4x4 to recover the special type if the elements appear to conform to one of the known optimized types. - \sa {QLoggingCategory::operator()}{operator()()}, data(), translate() + \sa {QMatrix4x4::}{operator()()}, data(), translate() */ void QMatrix4x4::optimize() { -- cgit v1.2.3