diff options
25 files changed, 57 insertions, 57 deletions
diff --git a/examples/qml/doc/src/qml-extending.qdoc b/examples/qml/doc/src/qml-extending.qdoc index f99aca5457..c5e3611905 100644 --- a/examples/qml/doc/src/qml-extending.qdoc +++ b/examples/qml/doc/src/qml-extending.qdoc @@ -171,7 +171,7 @@ is a little contrived, but in real applications it is likely that the two extensions would add additional properties or modify the Person classes behavior. -\section2 Define People as a base class +\section2 Define People as a Base Class The implementation of the People class itself has not changed since the previous example. However, as we have repurposed the People class as a common diff --git a/examples/quick/customitems/slideswitch/doc/src/example-slideswitch.qdoc b/examples/quick/customitems/slideswitch/doc/src/example-slideswitch.qdoc index 67a36eb8d8..d9703f6187 100644 --- a/examples/quick/customitems/slideswitch/doc/src/example-slideswitch.qdoc +++ b/examples/quick/customitems/slideswitch/doc/src/example-slideswitch.qdoc @@ -75,7 +75,7 @@ Item { the text will only be visible when the switch is on. -\section2 Images and user interaction +\section2 Images and User Interaction \snippet customitems/slideswitch/content/Switch.qml 4 First, we create the background image of the switch. diff --git a/examples/quick/demos/photoviewer/doc/src/photoviewer.qdoc b/examples/quick/demos/photoviewer/doc/src/photoviewer.qdoc index 9c0f8b337e..a107b19948 100644 --- a/examples/quick/demos/photoviewer/doc/src/photoviewer.qdoc +++ b/examples/quick/demos/photoviewer/doc/src/photoviewer.qdoc @@ -222,7 +222,7 @@ \printuntil onClicked \printuntil } - \section1 Laying out Photos on a Path + \section1 Laying Out Photos on a Path In AlbumDelegate.qml, we use a PathView type to lay out the photos provided by the \c visualModel.parts.stack model on a path that has the form of a diff --git a/src/imports/localstorage/plugin.cpp b/src/imports/localstorage/plugin.cpp index a7d95cc295..02cf125e48 100644 --- a/src/imports/localstorage/plugin.cpp +++ b/src/imports/localstorage/plugin.cpp @@ -563,7 +563,7 @@ The API conforms to the Synchronous API of the HTML5 Web Database API, The \l{Qt Quick Examples - Local Storage}{SQL Local Storage example} demonstrates the basics of using the Offline Storage API. -\section3 Open or create a databaseData +\section3 Open or Create a Database \code import QtQuick.LocalStorage 2.0 as Sql diff --git a/src/imports/testlib/TestCase.qml b/src/imports/testlib/TestCase.qml index 82211b5192..3fc3c0860a 100644 --- a/src/imports/testlib/TestCase.qml +++ b/src/imports/testlib/TestCase.qml @@ -49,7 +49,7 @@ import Qt.test.qtestroot 1.0 \since 4.8 \ingroup qtquicktest - \section1 Introduction to QML test cases + \section1 Introduction to QML Test Cases Test cases are written as JavaScript functions within a TestCase type: @@ -98,7 +98,7 @@ import Qt.test.qtestroot 1.0 once they have all completed. If a test case doesn't need to run (because a precondition has failed), then \l optional can be set to true. - \section1 Data-driven tests + \section1 Data-driven Tests Table data can be provided to a test using a function name that ends with "_data". Alternatively, the \c init_data() function can be used @@ -172,7 +172,7 @@ import Qt.test.qtestroot 1.0 To get the effect of the \c{QBENCHMARK_ONCE} macro, prefix the test function name with "benchmark_once_". - \section1 Simulating keyboard and mouse events + \section1 Simulating Keyboard and Mouse Events The keyPress(), keyRelease(), and keyClick() methods can be used to simulate keyboard events within unit tests. The events are diff --git a/src/imports/xmllistmodel/qqmlxmllistmodel.cpp b/src/imports/xmllistmodel/qqmlxmllistmodel.cpp index 61c8665a14..fc9f73a881 100644 --- a/src/imports/xmllistmodel/qqmlxmllistmodel.cpp +++ b/src/imports/xmllistmodel/qqmlxmllistmodel.cpp @@ -693,7 +693,7 @@ void QQuickXmlListModelPrivate::clear_role(QQmlListProperty<QQuickXmlListModelRo populated until the model is loaded. - \section2 Using key XML roles + \section2 Using Key XML Roles You can define certain roles as "keys" so that when reload() is called, the model will only add and refresh data that contains new values for diff --git a/src/qml/doc/src/cppintegration/data.qdoc b/src/qml/doc/src/cppintegration/data.qdoc index b5c5505628..723d6e4be1 100644 --- a/src/qml/doc/src/cppintegration/data.qdoc +++ b/src/qml/doc/src/cppintegration/data.qdoc @@ -329,7 +329,7 @@ them with default constructed values, do not use the indexed delete operator ("delete sequence[i]") but instead use the \c {splice} function ("sequence.splice(startIndex, deleteCount)"). -\section2 Value types +\section2 Value Types Some value types in Qt such as QPoint are represented in JavaScript as objects that have the same properties and functions like in the C++ API. The same diff --git a/src/qml/doc/src/qmllanguageref/documents/topic.qdoc b/src/qml/doc/src/qmllanguageref/documents/topic.qdoc index 840afa9a0e..bc104e9c8a 100644 --- a/src/qml/doc/src/qmllanguageref/documents/topic.qdoc +++ b/src/qml/doc/src/qmllanguageref/documents/topic.qdoc @@ -86,7 +86,7 @@ Please see the documentation about the \l{qtqml-syntax-basics.html} documentation about \l{qtqml-javascript-topic.html} {integrating QML and JavaScript} for in-depth information on that topic. -\section1 Defining Object Types through QML Documents +\section1 Defining Object Types Through QML Documents As described briefly in the previous section, a document implicitly defines a QML object type. One of the core principles of QML is the ability to define diff --git a/src/qml/doc/src/qmllanguageref/typesystem/objecttypes.qdoc b/src/qml/doc/src/qmllanguageref/typesystem/objecttypes.qdoc index b0aab1c73a..d1d28381b5 100644 --- a/src/qml/doc/src/qmllanguageref/typesystem/objecttypes.qdoc +++ b/src/qml/doc/src/qmllanguageref/typesystem/objecttypes.qdoc @@ -50,7 +50,7 @@ and registering the type with the QML engine, as discussed in \section1 Defining Object Types from QML -\section2 Defining Object Types through QML Documents +\section2 Defining Object Types Through QML Documents Plugin writers and application developers may provide types defined as QML documents. A QML document, when visible to the QML import system, defines a diff --git a/src/qml/doc/src/statemachine.qdoc b/src/qml/doc/src/statemachine.qdoc index 56a8746e1e..b0bfef4f69 100644 --- a/src/qml/doc/src/statemachine.qdoc +++ b/src/qml/doc/src/statemachine.qdoc @@ -61,7 +61,7 @@ \annotatedlist statemachine-qmltypes - \section1 Using both QtQuick and QtQml.StateMachine imports + \section1 Using Both QtQuick and QtQml.StateMachine Imports \warning If you're attempting to import both \l{QtQuick} and \e{QtQml.StateMachine} in one single QML file, make sure to import diff --git a/src/qml/types/qqmlbind.cpp b/src/qml/types/qqmlbind.cpp index da644becc2..91c5a50877 100644 --- a/src/qml/types/qqmlbind.cpp +++ b/src/qml/types/qqmlbind.cpp @@ -102,7 +102,7 @@ void QQmlBindPrivate::validate(QObject *binding) const In QML, property bindings result in a dependency between the properties of different objects. - \section1 Binding to an inaccessible property + \section1 Binding to an Inaccessible Property Sometimes it is necessary to bind an object's property to that of another object that isn't directly instantiated by QML, such as a @@ -120,7 +120,7 @@ void QQmlBindPrivate::validate(QObject *binding) const When \c{text} changes, the C++ property \c{enteredText} will update automatically. - \section1 Conditional bindings + \section1 Conditional Bindings In some cases you may want to modify the value of a property when a certain condition is met but leave it unmodified otherwise. Often, it's not possible diff --git a/src/quick/doc/src/advtutorial.qdoc b/src/quick/doc/src/advtutorial.qdoc index 6aeabbd7b5..025f902a6b 100644 --- a/src/quick/doc/src/advtutorial.qdoc +++ b/src/quick/doc/src/advtutorial.qdoc @@ -70,7 +70,7 @@ directory. \example tutorials/samegame/samegame1 -\section2 Creating the application screen +\section2 Creating the Application Screen The first step is to create the basic QML items in your application. @@ -92,7 +92,7 @@ and is used to give the button a more native look-and-feel. Notice the anchors for the \c Item, \c Button and \c Text types are set using group (dot) notation for readability. -\section2 Adding \c Button and \c Block components +\section2 Adding \c Button and \c Block Components The \c Button item in the code above is defined in a separate component file named \c Button.qml. To create a functional button, we use the QML types \l Text and \l MouseArea inside a \l Rectangle. @@ -138,7 +138,7 @@ types to get started. Next, we will populate the game canvas with some blocks. \example tutorials/samegame/samegame2 -\section2 Generating the blocks in JavaScript +\section2 Generating the Blocks in JavaScript Now that we've written some types, let's start writing the game. @@ -181,7 +181,7 @@ and moves the new block to its position on the game canvas. This involves severa \endlist -\section2 Connecting JavaScript components to QML +\section2 Connecting JavaScript Components to QML Now we need to call the JavaScript code in \c samegame.js from our QML files. To do this, we add this line to \c samegame.qml which imports @@ -212,7 +212,7 @@ Now, we have a screen of blocks, and we can begin to add the game mechanics. \example tutorials/samegame/samegame3 -\section2 Making a playable game +\section2 Making a Playable Game Now that we have all the game components, we can add the game logic that dictates how a player interacts with the blocks and plays the game @@ -230,7 +230,7 @@ To do this, we have added the following functions to \c samegame.js: As this is a tutorial about QML, not game design, we will only discuss \c handleClick() and \c victoryCheck() below since they interface directly with the QML types. Note that although the game logic here is written in JavaScript, it could have been written in C++ and then exposed to QML. -\section3 Enabling mouse click interaction +\section3 Enabling Mouse Click Interaction To make it easier for the JavaScript code to interface with the QML types, we have added an Item called \c gameCanvas to \c samegame.qml. It replaces the background as the item which contains the blocks. It also accepts mouse input from the user. Here is the item code: @@ -248,7 +248,7 @@ When clicked, the \l MouseArea calls \c{handleClick()} in \c samegame.js, which Note that if \c score was a global variable in the \c{samegame.js} file you would not be able to bind to it. You can only bind to QML properties. -\section3 Updating the score +\section3 Updating the Score When the player clicks a block and triggers \c handleClick(), \c handleClick() also calls \c victoryCheck() to update the score and to check whether the player has completed the game. Here is the \c victoryCheck() code: @@ -267,14 +267,14 @@ And this is how it is used in the main \c samegame.qml file: We give the dialog a \l {Item::z}{z} value of 100 to ensure it is displayed on top of our other components. The default \c z value for an item is 0. -\section3 A dash of color +\section3 A Dash of Color It's not much fun to play Same Game if all the blocks are the same color, so we've modified the \c createBlock() function in \c samegame.js to randomly create a different type of block (for either red, green or blue) each time it is called. \c Block.qml has also changed so that each block contains a different image depending on its type: \snippet tutorials/samegame/samegame3/Block.qml 0 -\section2 A working game +\section2 A Working Game Now we now have a working game! The blocks can be clicked, the player can score, and the game can end (and then you can start a new one). Here is a screenshot of what has been accomplished so far: @@ -298,7 +298,7 @@ until the next chapter - where your application becomes alive! \example tutorials/samegame/samegame4 -\section2 Adding some flair +\section2 Adding Some Flair Now we're going to do two things to liven up the game: animate the blocks and add a High Score system. @@ -307,7 +307,7 @@ JavaScript and QML files outside of \c samegame.qml have been moved into a new s In anticipation of the new block animations, \c Block.qml file is now renamed to \c BoomBlock.qml. -\section3 Animating block movement +\section3 Animating Block Movement First we will animate the blocks so that they move in a fluid manner. QML has a number of methods for adding fluid movement, and in this case we're going to use the \l Behavior type to add a \l SpringAnimation. @@ -324,7 +324,7 @@ This ensures the \l SpringAnimation on the \c x is only enabled after \c createB the correct position. Otherwise, the blocks will slide out of the corner (0,0) when a game begins, instead of falling from the top in rows. (Try commenting out \c {enabled: spawned} and see for yourself.) -\section3 Animating block opacity changes +\section3 Animating Block Opacity Changes Next, we will add a smooth exit animation. For this, we'll use a \l Behavior type, which allows us to specify a default animation when a property change occurs. In this case, when the \c opacity of a Block changes, we will @@ -353,7 +353,7 @@ Initially, we add these States to the root type of \c{BoomBlock.qml}: Now blocks will automatically fade in, as we already set \c spawned to true when we implemented the block animations. To fade out, we set \c dying to true instead of setting opacity to 0 when a block is destroyed (in the \c floodFill() function). -\section3 Adding particle effects +\section3 Adding Particle Effects Finally, we'll add a cool-looking particle effect to the blocks when they are destroyed. To do this, we first add a \l ParticleSystem in \c BoomBlock.qml, like so: @@ -374,7 +374,7 @@ player's actions. The end result is shown below, with a different set of images The theme change here is produced simply by replacing the block images. This can be done at runtime by changing the \l Image \c source property, so for a further challenge, you could add a button that toggles between themes with different images. -\section2 Keeping a High Scores table +\section2 Keeping a High Scores Table Another feature we might want to add to the game is a method of storing and retrieving high scores. @@ -409,7 +409,7 @@ The \c nameInputDialog is activated in the \c victoryCheck() function in \c same \dots 4 \snippet tutorials/samegame/samegame4/content/samegame.js 4 -\section3 Storing high scores offline +\section3 Storing High Scores Offline Now we need to implement the functionality to actually save the High Scores table. @@ -423,7 +423,7 @@ Then, we use the \l{QtQuick.LocalStorage}{Local Storage API} to maintain a persi This is one way of storing and displaying high scores locally, but certainly not the only way. A more complex alternative would be to create a high score dialog component, and pass it the results for processing and display (instead of reusing the \c Dialog). This would allow a more themeable dialog that could better present the high scores. If your QML is the UI for a C++ application, you could also have passed the score to a C++ function to store it locally in a variety of ways, including a simple format without SQL or in another SQL database. -\section3 Storing high scores online +\section3 Storing High Scores Online You've seen how you can store high scores locally, but it is also easy to integrate a web-enabled high score storage into your QML application. The implementation we've done her is very simple: the high score data is posted to a php script running on a server somewhere, and that server then stores it and @@ -445,7 +445,7 @@ An alternate way to access and submit web-based data would be to use QML types d makes it very easy to fetch and display XML based data such as RSS in a QML application (see the Flickr demo for an example). -\section2 That's it! +\section2 That's It! By following this tutorial you've seen how you can write a fully functional application in QML: diff --git a/src/quick/doc/src/concepts/layouts/qtquicklayouts-index.qdoc b/src/quick/doc/src/concepts/layouts/qtquicklayouts-index.qdoc index 0be66fad2c..f65b1152e9 100644 --- a/src/quick/doc/src/concepts/layouts/qtquicklayouts-index.qdoc +++ b/src/quick/doc/src/concepts/layouts/qtquicklayouts-index.qdoc @@ -43,7 +43,7 @@ \annotatedlist layouts - \section1 Related information + \section1 Related Information \list \li \l{Qt Quick} diff --git a/src/quick/doc/src/concepts/layouts/qtquicklayouts-overview.qdoc b/src/quick/doc/src/concepts/layouts/qtquicklayouts-overview.qdoc index e5834eb5c8..05e4465f2a 100644 --- a/src/quick/doc/src/concepts/layouts/qtquicklayouts-overview.qdoc +++ b/src/quick/doc/src/concepts/layouts/qtquicklayouts-overview.qdoc @@ -33,7 +33,7 @@ Qt Quick Layouts are items that are used to arrange items in a user interface. Since Qt Quick Layouts also resize their items, they are well suited for resizable user interfaces. - \section1 Getting started + \section1 Getting Started The QML types can be imported into your application using the following import statement in your \c {.qml} file. @@ -152,7 +152,7 @@ height specified in the QML file. - \section1 Connecting windows and layouts + \section1 Connecting Windows and Layouts You can just use normal anchoring concepts to ensure that the layout will follow the window resizing. diff --git a/src/quick/doc/src/concepts/modelviewsdata/cppmodels.qdoc b/src/quick/doc/src/concepts/modelviewsdata/cppmodels.qdoc index 12a107491a..8c647a5eaa 100644 --- a/src/quick/doc/src/concepts/modelviewsdata/cppmodels.qdoc +++ b/src/quick/doc/src/concepts/modelviewsdata/cppmodels.qdoc @@ -75,7 +75,7 @@ The API works just like with \l QStringList, as shown in the previous section. have changed. If the QVariantList changes, it will be necessary to reset the model. -\section2 QObjectList-based model +\section2 QObjectList-based Model A list of QObject* values can also be used as a model. A QList<QObject*> provides the properties of the objects in the list as roles. @@ -112,7 +112,7 @@ has changed. If the QList changes, it is necessary to reset the model by calling QQmlContext::setContextProperty() again. -\section2 QAbstractItemModel subclass +\section2 QAbstractItemModel Subclass A model can be defined by subclassing QAbstractItemModel. This is the best approach if you have a more complex model that cannot be supported diff --git a/src/quick/doc/src/concepts/statesanimations/animations.qdoc b/src/quick/doc/src/concepts/statesanimations/animations.qdoc index 1a2cff43f4..146902ecf1 100644 --- a/src/quick/doc/src/concepts/statesanimations/animations.qdoc +++ b/src/quick/doc/src/concepts/statesanimations/animations.qdoc @@ -139,7 +139,7 @@ values. \target qml-transition-animations -\section2 Transitions during State Changes +\section2 Transitions During State Changes \l{State}{Qt Quick States} are property configurations where a property may have different values to reflect different states. State changes introduce abrupt property changes; animations smooth transitions to produce visually diff --git a/src/quick/doc/src/concepts/visualcanvas/adaptations.qdoc b/src/quick/doc/src/concepts/visualcanvas/adaptations.qdoc index bcfdf311af..ba5b97da39 100644 --- a/src/quick/doc/src/concepts/visualcanvas/adaptations.qdoc +++ b/src/quick/doc/src/concepts/visualcanvas/adaptations.qdoc @@ -35,7 +35,7 @@ Originally Qt Quick always relied on OpenGL (OpenGL ES 2.0 or OpenGL 2.0) for pa the scene graph and rendering the results to a render target. From Qt 5.8 onwards Qt Quick also supports rendering in software and with Direct3D 12. -\section1 Switching between the adaptation used by the application +\section1 Switching Between the Adaptation Used by the Application The default rendering backend is still OpenGL, or - in Qt builds with disabled OpenGL support - the software renderer. This can be overridden either by using an environment variable @@ -261,7 +261,7 @@ offscreen render targets will be created with the specified sample count and a quality of the maximum supported quality level. The backend automatically performs resolving into the non-multisample swapchain buffers after each frame. -\section2 Semi-transparent windows +\section2 Semi-transparent Windows When the alpha channel is enabled either via QQuickWindow::setDefaultAlphaBuffer() or by setting alphaBufferSize to a @@ -286,7 +286,7 @@ power-of-two images at the moment. Textures of other size will work too, but this involves a QImage-based scaling on the CPU first. Therefore avoid enabling mipmapping for NPOT images whenever possible. -\section2 Image formats +\section2 Image Formats When creating textures via the C++ scenegraph APIs like QQuickWindow::createTextureFromImage(), 32-bit formats will not involve any diff --git a/src/quick/doc/src/concepts/visualcanvas/scenegraph.qdoc b/src/quick/doc/src/concepts/visualcanvas/scenegraph.qdoc index cb14c72b04..a7666d725e 100644 --- a/src/quick/doc/src/concepts/visualcanvas/scenegraph.qdoc +++ b/src/quick/doc/src/concepts/visualcanvas/scenegraph.qdoc @@ -540,7 +540,7 @@ with multiple windows. and may trigger early-z when available, but again, setting Item::visible to false is always faster. - \section2 Mixing with 3D primitives + \section2 Mixing with 3D Primitives The scene graph can support pseudo 3D and proper 3D primitives. For instance, one can implement a "page curl" effect using a diff --git a/src/quick/doc/src/tutorial.qdoc b/src/quick/doc/src/tutorial.qdoc index e44129de83..6084a8a686 100644 --- a/src/quick/doc/src/tutorial.qdoc +++ b/src/quick/doc/src/tutorial.qdoc @@ -99,7 +99,7 @@ In this case, we specify that our text type should be horizontally centered in t The \c font.pointSize and \c font.bold properties are related to fonts and use the dot notation. -\section2 Viewing the example +\section2 Viewing the Example To view what you have created, run the \l{Prototyping with qmlscene}{qmlscene} tool (located in the \c bin directory) with your filename as the first argument. For example, to run the provided completed Tutorial 1 example from the install location, you would type: @@ -167,7 +167,7 @@ the same size as its parent. A \l MouseArea defines a signal called \e clicked. When this signal is triggered we want to emit our own \e clicked signal with the color as parameter. -\section2 The main QML file +\section2 The Main QML File In our main QML file, we use our \c Cell component to create the color picker: diff --git a/src/quick/items/qquickitemviewtransition.cpp b/src/quick/items/qquickitemviewtransition.cpp index 04d93937eb..745e5b275f 100644 --- a/src/quick/items/qquickitemviewtransition.cpp +++ b/src/quick/items/qquickitemviewtransition.cpp @@ -639,7 +639,7 @@ QQuickViewTransitionAttached::QQuickViewTransitionAttached(QObject *parent) attached property can be used to augment view transitions. - \section2 View transitions: a simple example + \section2 View Transitions: a Simple Example Here is a basic example of the use of view transitions. The view below specifies transitions for the \c add and \c displaced properties, which will be run when items are added to the view: @@ -668,7 +668,7 @@ QQuickViewTransitionAttached::QQuickViewTransitionAttached(QObject *parent) are some examples of how this can be achieved. - \section2 Using the ViewTransition attached property + \section2 Using the ViewTransition Attached Property As stated, the various ViewTransition properties provide details specific to the individual item being transitioned as well as the operation that triggered the transition. In the animation above, @@ -719,7 +719,7 @@ QQuickViewTransitionAttached::QQuickViewTransitionAttached(QObject *parent) that is triggered by a particular add operation. - \section3 Delaying animations based on index + \section3 Delaying Animations Based on Index Since each view transition is run once for each item affected by the transition, the ViewTransition properties can be used within a transition to define custom behavior for each item's transition. @@ -738,7 +738,7 @@ QQuickViewTransitionAttached::QQuickViewTransitionAttached(QObject *parent) \image viewtransitions-delayedbyindex.gif - \section3 Animating items to intermediate positions + \section3 Animating Items to Intermediate Positions The ViewTransition.item property gives a reference to the item to which the transition is being applied. This can be used to access any of the item's attributes, custom \c property values, @@ -775,7 +775,7 @@ QQuickViewTransitionAttached::QQuickViewTransitionAttached(QObject *parent) \image viewtransitions-pathanim.gif - \section2 Handling interrupted animations + \section2 Handling Interrupted Animations A view transition may be interrupted at any time if a different view transition needs to be applied while the original transition is in progress. For example, say Item A is inserted at index 0 @@ -819,7 +819,7 @@ QQuickViewTransitionAttached::QQuickViewTransitionAttached(QObject *parent) properties. - \section2 Restrictions regarding ScriptAction + \section2 Restrictions Regarding ScriptAction When a view transition is initialized, any property bindings that refer to the ViewTransition attached property are evaluated in preparation for the transition. Due to the nature of the diff --git a/src/quick/items/qquickshadereffect.cpp b/src/quick/items/qquickshadereffect.cpp index a41e9324f3..8f0866f417 100644 --- a/src/quick/items/qquickshadereffect.cpp +++ b/src/quick/items/qquickshadereffect.cpp @@ -475,7 +475,7 @@ QT_BEGIN_NAMESPACE \li \snippet qml/opacitymask.qml 1 \endtable - \section1 Other notes + \section1 Other Notes By default, the ShaderEffect consists of four vertices, one for each corner. For non-linear vertex transformations, like page curl, you can diff --git a/src/quick/items/qquickwindow.cpp b/src/quick/items/qquickwindow.cpp index 07b3d538e5..b58caa061a 100644 --- a/src/quick/items/qquickwindow.cpp +++ b/src/quick/items/qquickwindow.cpp @@ -1226,7 +1226,7 @@ void QQuickWindowPrivate::cleanup(QSGNode *n) \note All classes with QSG prefix should be used solely on the scene graph's rendering thread. See \l {Scene Graph and Rendering} for more information. - \section2 Context and surface formats + \section2 Context and Surface Formats While it is possible to specify a QSurfaceFormat for every QQuickWindow by calling the member function setFormat(), windows may also be created from diff --git a/src/quick/util/qquickimageprovider.cpp b/src/quick/util/qquickimageprovider.cpp index c80025f968..4eab5608b1 100644 --- a/src/quick/util/qquickimageprovider.cpp +++ b/src/quick/util/qquickimageprovider.cpp @@ -245,7 +245,7 @@ void QQuickImageResponse::cancel() If you want the rest of the URL to be case insensitive, you will have to take care of that yourself inside your image provider. - \section2 An example + \section2 An Example Here are two images. Their \c source values indicate they should be loaded by an image provider named "colors", and the images to be loaded are "yellow" @@ -291,7 +291,7 @@ void QQuickImageResponse::cancel() instead of registering it in the application \c main() function as shown above. - \section2 Asynchronous image loading + \section2 Asynchronous Image Loading Image providers that support QImage or Texture loading automatically include support for asychronous loading of images. To enable asynchronous loading for an @@ -320,7 +320,7 @@ void QQuickImageResponse::cancel() See the \l {imageresponseprovider}{Image Response Provider Example} for a complete implementation. - \section2 Image caching + \section2 Image Caching Images returned by a QQuickImageProvider are automatically cached, similar to any image loaded by the QML engine. When an image with a diff --git a/src/quick/util/qquickpropertychanges.cpp b/src/quick/util/qquickpropertychanges.cpp index 8d76bd986f..61380b3ea0 100644 --- a/src/quick/util/qquickpropertychanges.cpp +++ b/src/quick/util/qquickpropertychanges.cpp @@ -101,7 +101,7 @@ QT_BEGIN_NAMESPACE \l {Item::}{parent} value, use ParentChange instead. - \section2 Resetting property values + \section2 Resetting Property Values The \c undefined value can be used to reset the property value for a state. In the following example, when \c myText changes to the \e widerText @@ -111,7 +111,7 @@ QT_BEGIN_NAMESPACE \snippet qml/propertychanges.qml reset - \section2 Immediate property changes in transitions + \section2 Immediate Property Changes in Transitions When \l{Animation and Transitions in Qt Quick}{Transitions} are used to animate state changes, they animate properties from their values in the current diff --git a/src/quickwidgets/qquickwidget.cpp b/src/quickwidgets/qquickwidget.cpp index 2c3c72d5f1..c23d11ed20 100644 --- a/src/quickwidgets/qquickwidget.cpp +++ b/src/quickwidgets/qquickwidget.cpp @@ -423,7 +423,7 @@ QImage QQuickWidgetPrivate::grabFramebuffer() entire purpose of QQuickWidget is to render Quick scenes without a separate native window, hence making it a native widget should always be avoided. - \section1 Scene graph and context persistency + \section1 Scene Graph and Context Persistency QQuickWidget honors QQuickWindow::isPersistentSceneGraph(), meaning that applications can decide - by calling |