AuroraMiddleware/qt5base-lts
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Doc: Fix broken links

Browse Source 
Change-Id: Ic275dfbf0b332fc34ea0fac1c31c4935ad961527
Reviewed-by: Frederik Gladhorn <frederik.gladhorn@digia.com>
This commit is contained in:
Sze Howe Koh 2014-02-01 23:30:08 +08:00 committed by The Qt Project
parent 6894bc0f3f
commit 8bb5dba0cb
19 changed files with 31 additions and 39 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
qmake/doc/src/qmake-manual.qdoc
View File

@ -716,7 +716,7 @@
and \l{QMAKE_FRAMEWORK_VERSION} variables. By default, the values used for
these variables are obtained from the \l{TARGET} and \l{VERSION} variables.
See \l{Deploying an Application on Mac OS X} for more information about
See \l{Qt for Mac OS X - Deployment} for more information about
deploying applications and libraries.
\section2 Creating and Moving Xcode Projects
@ -810,7 +810,7 @@
\snippet code/doc_src_qmake-manual.pro 23
This is discussed in more detail in the
\l{Deploying an Application on Windows#Manifest files}
\l{Qt for Windows - Deployment#Manifest files}
{deployment guide for Windows}.
*/
@ -1999,7 +1999,7 @@
platform, the variable will be forwarded to the MACOSX_DEPLOYMENT_TARGET
environment variable, which is interpreted by the compiler or linker.
For more information, see the
\l{Deploying an Application on Mac OS X#Mac OS X Version Dependencies}{Deploying
\l{Qt for Mac OS X - Deployment#Mac OS X Version Dependencies}{Deploying
an Application on Mac OS X} document.
\section1 QMAKE_MAKEFILE
@ -2092,7 +2092,6 @@
\row \li dbus \li \l{Qt D-Bus}
\row \li declarative \li \l{Qt Quick 1} (deprecated)
\row \li designer \li \l{Qt Designer}
\row \li designercomponents \li \l{Qt Designer Components}
\row \li gui (included by default) \li \l{Qt GUI}
\row \li help \li \l{Qt Help}
\row \li multimedia \li \l{Qt Multimedia}
@ -3273,7 +3272,7 @@
\li \l{QMAKE_EXT_UI} modifies the extension used for \QD UI files
(usually in \l{FORMS}).
\li \l{QMAKE_EXT_PRL} modifies the extension placed on
\l{#LibDepend}{library dependency files}.
\l{LibDepend}{library dependency files}.
\li \l{QMAKE_EXT_LEX} changes the suffix used in Lex files (usually in
\l{LEXSOURCES}).
\li \l{QMAKE_EXT_YACC} changes the suffix used in Yacc files (usually in
@ -4335,8 +4334,7 @@
them uses project-specific variables to customize output files.
Platform-specific variables are not described here. For more information,
see \l{Deploying an Application on Windows} and
\l{Developing Qt Applications for Mac OS X}.
see \l{Qt for Windows - Deployment} and \l{Qt for Mac OS X}.
\target Application
\section1 Building an Application

2
src/corelib/doc/qtcore.qdocconf
View File

@ -26,7 +26,7 @@ qhp.QtCore.subprojects.classes.sortPages = true
tagfile = ../../../doc/qtcore/qtcore.tags
depends += qtgui qtwidgets qtnetwork qtdoc qtquick qtlinguist qtdesigner qtconcurrent qtxml qmake
depends += qtgui qtwidgets qtnetwork qtdoc qtmacextras qtquick qtlinguist qtdesigner qtconcurrent qtxml qmake
headerdirs += ..

8
src/corelib/global/qglobal.cpp
View File

@ -1960,7 +1960,7 @@ const QSysInfo::WinVersion QSysInfo::WindowsVersion = QSysInfo::windowsVersion()
conditions that it would not otherwise know about. However, there is no
guarantee that the compiler will actually use those hints.
This macro could be considered a "lighter" version of \l{Q_ASSERT}. While
This macro could be considered a "lighter" version of \l{Q_ASSERT()}. While
Q_ASSERT will abort the program's execution if the condition is false,
Q_ASSUME will tell the compiler not to generate code for those conditions.
Therefore, it is important that the assumptions always hold, otherwise
@ -3318,7 +3318,7 @@ bool QInternal::activateCallbacks(Callback cb, void **parameters)
If you need C++11 noexcept semantics, don't use this macro, use
Q_DECL_NOEXCEPT/Q_DECL_NOEXCEPT_EXPR instead.
\sa Q_DECL_NOEXCEPT, Q_DECL_NOEXCEPT_EXPR
\sa Q_DECL_NOEXCEPT, Q_DECL_NOEXCEPT_EXPR()
*/
/*!
@ -3372,7 +3372,7 @@ bool QInternal::activateCallbacks(Callback cb, void **parameters)
function can't possibly throw, don't use this macro, use
Q_DECL_NOTHROW instead.
\sa Q_DECL_NOTHROW, Q_DECL_NOEXCEPT_EXPR
\sa Q_DECL_NOTHROW, Q_DECL_NOEXCEPT_EXPR()
*/
/*!
@ -3394,7 +3394,7 @@ bool QInternal::activateCallbacks(Callback cb, void **parameters)
function can't possibly throw, don't use this macro, use
Q_DECL_NOTHROW instead.
\sa Q_DECL_NOTHROW, Q_DECL_NOEXCEPT_EXPR
\sa Q_DECL_NOTHROW, Q_DECL_NOEXCEPT
*/
/*!

2
src/corelib/io/qloggingcategory.cpp
View File

@ -72,7 +72,7 @@ Q_GLOBAL_STATIC_WITH_ARGS(QLoggingCategory, qtDefaultCategory,
\section1 Checking category configuration
QLoggingCategory provides \l isDebugEnabled(), \l isWarningEnabled(),
\l isCriticalEnabled(), \l isTraceEnabled(), as well as \l isEnabled()
\l isCriticalEnabled(), as well as \l isEnabled()
to check whether messages for the given message type should be logged.
\note The qCDebug(), qCWarning(), qCCritical() macros prevent arguments

6
src/corelib/kernel/qvariant.cpp
View File

@ -2833,8 +2833,8 @@ static bool canConvertMetaObject(int fromId, int toId, QObject *fromObject)
\snippet code/src_corelib_kernel_qvariant.cpp 10
\sa convert(), QSequentialIterable, qRegisterSequentialConverter(), QAssociativeIterable,
qRegisterAssociativeConverter()
\sa convert(), QSequentialIterable, Q_DECLARE_SEQUENTIAL_CONTAINER_METATYPE(), QAssociativeIterable,
Q_DECLARE_ASSOCIATIVE_CONTAINER_METATYPE()
*/
bool QVariant::canConvert(int targetTypeId) const
{
@ -3334,7 +3334,7 @@ QDebug operator<<(QDebug dbg, const QVariant::Type p)
\snippet code/src_corelib_kernel_qvariant.cpp 9
\sa setValue(), fromValue(), canConvert(), qRegisterSequentialConverter()
\sa setValue(), fromValue(), canConvert(), Q_DECLARE_SEQUENTIAL_CONTAINER_METATYPE()
*/
/*! \fn bool QVariant::canConvert() const

2
src/corelib/tools/qstring.cpp
View File

@ -7691,7 +7691,7 @@ QString &QString::setRawData(const QChar *unicode, int size)
\snippet code/src_corelib_tools_qstring.cpp 6
\sa QString, QLatin1Char, QStringLiteral
\sa QString, QLatin1Char, {QStringLiteral()}{QStringLiteral}
*/
/*! \fn QLatin1String::QLatin1String(const char *str)

2
src/gui/accessible/qaccessibleplugin.cpp
View File

@ -87,8 +87,6 @@ QAccessiblePlugin::~QAccessiblePlugin()
Creates and returns a QAccessibleInterface implementation for the
class \a key and the object \a object. Keys are case sensitive.
\sa keys()
*/
QT_END_NAMESPACE

3
src/gui/doc/qtgui.qdocconf
View File

@ -29,6 +29,9 @@ tagfile = ../../../doc/qtgui/qtgui.tags
depends += \
qtcore \
qtimageformats \
qtmacextras \
qtmultimedia \
qtnetwork \
qtopengl \
qtsvg \

2
src/gui/image/qpictureformatplugin.cpp
View File

@ -79,8 +79,6 @@ QT_BEGIN_NAMESPACE
Installs a QPictureIO picture I/O handler for the picture format \a
format. Returns \c true on success.
\sa keys()
*/

2
src/gui/kernel/qgenericplugin.cpp
View File

@ -95,8 +95,6 @@ QGenericPlugin::~QGenericPlugin()
Implement this function to create a driver matching the type
specified by the given \a key and \a specification parameters. Note that
keys are case-insensitive.
\sa keys()
*/
QT_END_NAMESPACE

4
src/gui/kernel/qwindow.cpp
View File

@ -79,8 +79,8 @@ QT_BEGIN_NAMESPACE
QWindow directly. Still, it is possible to render directly to a QWindow
with QBackingStore or QOpenGLContext, when wanting to keep dependencies to
a minimum or when wanting to use OpenGL directly. The
\l{gui/rasterwindow}{Raster Window} and \l{gui/openglwindow}{OpenGL Window}
examples are useful reference examples for how to render to a QWindow using
\l{Raster Window Example} and \l{OpenGL Window Example}
are useful reference examples for how to render to a QWindow using
either approach.
\section1 Resource management

5
src/opengl/doc/src/qtopengl-examples.qdoc
View File

@ -33,9 +33,8 @@
\image opengl-examples.png
These examples describe how to use the Qt OpenGL Module. For new code,
please use the OpenGL classes in the \l QtGui module.
These examples describe how to use the \l {Qt OpenGL} module. For new code,
please use the OpenGL classes in the \l {Qt GUI} module.
Qt provides support for integration with OpenGL implementations on all
platforms, giving developers the opportunity to display hardware accelerated

2
src/opengl/qglframebufferobject.cpp
View File

@ -779,7 +779,7 @@ void QGLFramebufferObjectPrivate::init(QGLFramebufferObject *q, const QSize &sz,
\note This class has been deprecated in favor of QOpenGLFramebufferObject.
\sa {Framebuffer Object Example}
\sa {Framebuffer Object 2 Example}
*/

2
src/opengl/qglpixelbuffer.cpp
View File

@ -90,7 +90,7 @@
Pbuffers are provided by the OpenGL \c pbuffer extension; call
hasOpenGLPbuffer() to find out if the system provides pbuffers.
\sa {opengl/pbuffers}{Pbuffers Example}
\sa {Pixel Buffers Example}
*/
#include <private/qopenglextensions_p.h>

3
src/tools/qdoc/doc/qdoc-manual-contextcmds.qdoc
View File

@ -314,8 +314,7 @@
\endcode
See how QDoc renders this property on the reference page for the
\l {changes-prop} {State}
type.
\l {State::changes}{State} type.
\target obsolete-command
\section1 \\obsolete

5
src/tools/qdoc/doc/qdoc-manual-intro.qdoc
View File

@ -79,9 +79,8 @@
* /
\endcode
From the QDoc comment above, QDoc generates the HTML page
\l {details}
{QObject Class Reference}.
From the QDoc comment above, QDoc generates the HTML \l {QObject}
{QObject class reference} page.
This manual explains how to use the QDoc commands in QDoc comments
to embed good documentation in your source files. It also explains

2
src/widgets/kernel/qaction.cpp
View File

@ -270,7 +270,7 @@ void QActionPrivate::setShortcutEnabled(bool enable, QShortcutMap &map)
\value AboutQtRole This action matches handles the "About Qt" menu item.
\value AboutRole This action should be placed where the "About" menu item is in the application menu. The text of
the menu item will be set to "About <application name>". The application name is fetched from the
\c{Info.plist} file in the application's bundle (See \l{Deploying an Application on Mac OS X}).
\c{Info.plist} file in the application's bundle (See \l{Qt for Mac OS X - Deployment}).
\value PreferencesRole This action should be placed where the "Preferences..." menu item is in the application menu.
\value QuitRole This action should be placed where the Quit menu item is in the application menu.

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

@ -7004,7 +7004,7 @@ void QWidget::setUpdatesEnabled(bool enable)
depending on the platform's default behavior for the window flags.
\sa raise(), showEvent(), hide(), setVisible(), showMinimized(), showMaximized(),
showNormal(), isVisible(), windowFlags(), flags()
showNormal(), isVisible(), windowFlags()
*/
void QWidget::show()
{

4
src/widgets/widgets/qmenubar.cpp
View File

@ -666,8 +666,8 @@ void QMenuBar::initStyleOption(QStyleOptionMenuItem *option, const QAction *acti
\b{Note:} The text used for the application name in the menu
bar is obtained from the value set in the \c{Info.plist} file in
the application's bundle. See \l{Deploying an Application on
Mac OS X} for more information.
the application's bundle. See \l{Qt for Mac OS X - Deployment}
for more information.
\section1 QMenuBar on Windows CE