\printuntil }
The \c onTriggered signal handler is called when the timer is triggered to
- increment the value of the the \c countdown custom property.
+ increment the value of the \c countdown custom property.
We set the \c repeat property to \c true to specify that the timer is
triggered at the interval of 1 second as long as the value of \c countdown
We use anchoring to position the help button at the bottom center of the
game canvas.
- We use another \l{Image} type to to display the help image:
+ We use another \l{Image} type to display the help image:
\printuntil }
\printuntil }
opaque, otherwise their opacity is set to \c 0.4.
We use a \l{Text} type to display the cost of each tower item, as specified
- by the the \c towerData variable, depending on \c towerType:
+ by the \c towerData variable, depending on \c towerType:
\skipto Text
\printuntil }
\snippet scenegraph/customgeometry/beziercurve.cpp 6
- The scene graph API provides a few commonly used used material
+ The scene graph API provides a few commonly used material
implementations. In this example we use the QSGFlatColorMaterial
which will fill the shape defined by the geometry with a solid
color. Again we pass the ownership of the material to the node, so
/*!
\qmlproperty url FolderListModel::parentFolder
- Returns the URL of the parent of of the current \l folder.
+ Returns the URL of the parent of the current \l folder.
*/
QUrl QQuickFolderListModel::parentFolder() const
{
\inqmlmodule QtQuick.Particles 2
\ingroup qtquick-particles
\inherits Affector
- \brief For applying accleration in an angle
+ \brief For applying acceleration in an angle
This element will accelerate all affected particles to a vector of
the specified magnitude in the specified angle. If the angle and acceleration do
all property values have been initialized.
The \l {Qt QML} module provides the QQmlParserStatus to be subclassed for these
-purposes. It defines a number of virtual methods that are invoked invoked at
+purposes. It defines a number of virtual methods that are invoked at
various stages during component instantiation. To receive these notifications, a
C++ class should inherit QQmlParserStatus and also notify the Qt meta system
using the Q_INTERFACES() macro.
In general, these are accessible from QML regardless of whether a
QObject-derived class has been \l{Registering C++ types with the QML type
-system}{registered with the QML type system}. However, if if a class is to be
+system}{registered with the QML type system}. However, if a class is to be
used in a way that requires the engine to access additional type information
— for example, if the class itself is to be used as a method parameter or
property, or if one of its enum types is to be used in this way — then the
The use of Q_INVOKABLE makes the \c clearChart() method available to the
Qt Meta-Object system, and in turn, to QML. Note that it could have
-been declared as as a Qt slot instead of using Q_INVOKABLE, as
+been declared as a Qt slot instead of using Q_INVOKABLE, as
slots are also callable from QML. Both of these approaches are valid.
The \c clearChart() method simply changes the color to Qt::transparent,
System#Attached Signal Handlers}{attached signal} when its instantiation is
complete. JavaScript code in the corresponding \c{Component.onCompleted} handler
runs after the object is instantiated. Thus, the best place to write application
-startup code is in the \c{Component.onCompleted} handler of the top-level level
+startup code is in the \c{Component.onCompleted} handler of the top-level
object, because this object emits \c{Component.completed} when the QML environment
is fully established.
An identified module has several restrictions upon it:
\list
-\li an identified module must must be installed into the
+\li an identified module must be installed into the
\l{qtqml-syntax-imports.html#qml-import-path}{QML import path}
\li the module identifier specified in the \l{qtqml-modules-qmldir.html}
{module identifier directive} must match the install path of the module
The ability to import a local directory is convenient for cases such as
in-application component sets and application prototyping, although any code
-that imports such modules must must update their relevant \c import statements
+that imports such modules must update their relevant \c import statements
if the module directory moves to another location. This can be avoided if
\l{qtqml-modules-identifiedmodules.html}{QML modules} are used instead,
as an installed module is imported with a unique identifier string rather than
The \c rect type refers to a value with \c x, \c y, \c width and \c height attributes.
For example, to read the \c width and \c height values of the \l Item
-\l {Item::childrenRect.x}{childrenRect} rect-type type property:
+\l {Item::childrenRect.x}{childrenRect} rect-type property:
\qml
Rectangle {
/*
\enum QQmlAbstractUrlInterceptor::DataType
- Specifies where URL interception is taking place place.
+ Specifies where URL interception is taking place.
Because QML loads qmldir files for locating types, there are two URLs involved in loading a QML type. The URL of the (possibly implicit) qmldir used for locating the type and the URL of the file which defines the type. Intercepting
both leads to either complex URL replacement or double URL replacements for the same file.
placeholder items that are later \l {resolve()}{resolved} to real model data when it becomes
available.
- Delegate items can also be be instantiated directly from a DelegateModelGroup using the
+ Delegate items can also be instantiated directly from a DelegateModelGroup using the
create() function, making it possible to use DelegateModel without an accompanying view
type or to cherry-pick specific items that should be instantiated irregardless of whether
they're currently within a view's visible area.
The ListView type has the \c section
\l{qtqml-syntax-objectattributes.html#Attached-properties-and-attached-signal-handlers}
{attached property} that can combine adjacent and related types into a
- section. The section's \c property property is for selecting which list
- type property to use as sections. The \c criteria can dictate how the
- section names are displayed and the \c delegate is similar to the views'
+ section. The \c section.property determines which list
+ type property to use as sections. The \c section.criteria can dictate how the
+ section names are displayed and the \c section.delegate is similar to the views'
\l {qml-view-delegate}{delegate} property.
\snippet qml/listview-sections.qml section
\image listview-section.png
mirrored, but positioning of the content (like application layouts and the flow of visual elements) is
mirrored. For example, photos shown in chronological order should flow from right to left, the
low end range of the horizontal sliders should be located at the right side of the slider, and
-text lines should should be aligned to the right side of the available text area. The location of visual
+text lines should be aligned to the right side of the available text area. The location of visual
elements should not be mirrored when the position is related to a content; for example, when a
position marker is shown to indicate a location on a map. Also, there are some special cases you may
need to take into account where right-to-left language speakers are used to left-to-right
application is allowed to draw.
The \l {Scene Graph - OpenGL Under QML} example gives an example on
-how to use use these signals.
+how to use these signals.
The other alternative is to create a QQuickFramebufferObject, render
into it, and let it be displayed in the scene graph as a texture.
Adds a quadratic bezier curve between the current point and the endpoint (\c x, \c y) with the control point specified by (\c cpx, \c cpy).
- See \l{http://www.w3.org/TR/2dcontext/#dom-context-2d-quadraticcurveto}{W3C 2d context standard for for quadraticCurveTo}
+ See \l{http://www.w3.org/TR/2dcontext/#dom-context-2d-quadraticcurveto}{W3C 2d context standard for quadraticCurveTo}
*/
QV4::ReturnedValue QQuickJSContext2DPrototype::method_quadraticCurveTo(QV4::CallContext *ctx)
{
/*!
\fn void QQuickItem::sceneGraphInitialized()
- This signal is emitted when the scene graph is is initialized for
+ This signal is emitted when the scene graph is initialized for
items that have the ItemHasContents flag set.
When the scene graph is using a dedicated render thread, this
This means that for all x values before the first character this function returns 0,
and for all x values after the last character this function returns text.length. If
the y value is above the text the position will be that of the nearest character on
- the first line line and if it is below the text the position of the nearest character
+ the first line and if it is below the text the position of the nearest character
on the last line will be returned.
The cursor position type specifies how the cursor position should be resolved.
When an item is moved into a new focus scope (either being added to a window
for the first time, or having its parent changed), if the focus scope already has
a scope focused item that takes precedence over the item being added. Otherwise,
-the focus of the added tree is used. In the case of of a tree of items being
+the focus of the added tree is used. In the case of a tree of items being
added to a window for the first time, which may have a conflicted focus state (two
or more items in one scope having focus set), the same rule is applied item by item -
thus the first item that has focus will get it (assuming the scope doesn't already
\qmlattachedproperty QWindow::Visibility Window::visibility
\since 5.4
- This attached property holds whether whether the window is currently shown
+ This attached property holds whether the window is currently shown
in the windowing system as normal, minimized, maximized, fullscreen or
hidden. The Window attached property can be attached to any Item. If the
item is not shown in any window, the value will be \l {QWindow::}{Hidden}.
arbitrary input textures, such as YUV video frames or 8 bit alpha
masks. The scene graph backend provides a default implementation
of normal color textures. As the implementation of these may be
- hardware specific, they are are constructed via the factory
+ hardware specific, they are constructed via the factory
function QQuickWindow::createTextureFromImage().
The texture is a wrapper around an OpenGL texture, which texture
projects / platform / upstream / qtdeclarative.git / commitdiff