<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE html>
<html lang="en">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<!-- topic.qdoc -->
<title>Important Concepts In Qt Quick - User Input | Qt Quick 5.12.6</title>
<link rel="stylesheet" type="text/css" href="style/offline-simple.css" />
<script type="text/javascript">
document.getElementsByTagName("link").item(0).setAttribute("href", "style/offline.css");
// loading style sheet breaks anchors that were jumped to before
// so force jumping to anchor again
setTimeout(function() {
var anchor = location.hash;
// need to jump to different anchor first (e.g. none)
location.hash = "#";
setTimeout(function() {
location.hash = anchor;
}, 0);
}, 0);
</script>
</head>
<body>
<div class="header" id="qtdocheader">
<div class="main">
<div class="main-rounded">
<div class="navigationbar">
<table><tr>
<td >Qt 5.12</td><td ><a href="qtquick-index.html">Qt Quick</a></td><td >Important Concepts In Qt Quick - User Input</td></tr></table><table class="buildversion"><tr>
<td id="buildversion" width="100%" align="right"><a href="qtquick-index.html">Qt 5.12.6 Reference Documentation</a></td>
</tr></table>
</div>
</div>
<div class="content">
<div class="line">
<div class="content mainContent">
<div class="sidebar">
<div class="toc">
<h3><a name="toc">Contents</a></h3>
<ul>
<li class="level1"><a href="#input-from-pointing-devices">Input from Pointing Devices</a></li>
<li class="level1"><a href="#keyboard-input-and-keyboard-focus">Keyboard Input and Keyboard Focus</a></li>
<li class="level1"><a href="#device-motion-gestures">Device Motion Gestures</a></li>
</ul>
</div>
<div class="sidebar-content" id="sidebar-content"></div></div>
<h1 class="title">Important Concepts In Qt Quick - User Input</h1>
<span class="subtitle"></span>
<!-- $$$qtquick-input-topic.html-description -->
<div class="descr"> <a name="details"></a>
<p>Being able to respond to user-input is a fundamental part of user-interface design. Depending on the use-case that an application solves, and the form-factor of the device that the application runs on, the best way to receive user-input may be different.</p>
<a name="input-from-pointing-devices"></a>
<h2 id="input-from-pointing-devices">Input from Pointing Devices</h2>
<p>Allowing users to physically touch a screen to interact with an application is a popular user-interface paradigm on portable devices like smartphones and tablets. In desktop applications, detecting and reacting to clicks and presses according to the mouse cursor position is a fundamental concept in user-interface design.</p>
<p>Touch-driven and mouse-driven user interfaces are supported by various <a href="qtquickhandlers-index.html">input handler</a> types, and visual object types such as <a href="qml-qtquick-flickable.html">Flickable</a> and <a href="qml-qtquick-mousearea.html">MouseArea</a>.</p>
<p>See also the documentation about <a href="qtquick-input-mouseevents.html">mouse events in Qt Quick</a>.</p>
<a name="keyboard-input-and-keyboard-focus"></a>
<h2 id="keyboard-input-and-keyboard-focus">Keyboard Input and Keyboard Focus</h2>
<p>Supporting input from a keyboard is a vital component of the user interface of many applications.</p>
<p>Any visual item can receive keyboard input through the <a href="qml-qtquick-keys.html">Keys</a> attached type. Additionally, the issue of <i>keyboard focus</i> arises when multiple items are required to receive key events, as these events must be passed to the correct item. See the documentation about <a href="qtquick-input-focus.html">Keyboard focus in Qt Quick</a> for more information on this topic.</p>
<p>Qt Quick also provides visual text items which automatically receive keyboard events and key-presses, and displays the appropriate text. See the documentation about <a href="qtquick-input-textinput.html">text input</a> for in-depth information on the topic.</p>
<a name="device-motion-gestures"></a>
<h2 id="device-motion-gestures">Device Motion Gestures</h2>
<p>Detecting device gestures with an accelerometer, or through camera-based gesture recognition, can allow users to interact with an application without requiring their full and undevided attention. It can also provide a more interactive and engaging experience.</p>
<p>Qt Quick itself does not offer first-class support for physical device motion gestures; however, the Qt Sensors module provides QML types with support for such gestures. See the Qt Sensors module documentation for more information on the topic.</p>
</div>
<!-- @@@qtquick-input-topic.html -->
</div>
</div>
</div>
</div>
</div>
<div class="footer">
<p>
<acronym title="Copyright">©</acronym> 2019 The Qt Company Ltd.
Documentation contributions included herein are the copyrights of
their respective owners.<br/> The documentation provided herein is licensed under the terms of the <a href="http://www.gnu.org/licenses/fdl.html">GNU Free Documentation License version 1.3</a> as published by the Free Software Foundation.<br/> Qt and respective logos are trademarks of The Qt Company Ltd. in Finland and/or other countries worldwide. All other trademarks are property
of their respective owners. </p>
</div>
</body>
</html>
distrib
>
Mageia
>
7
>
i586
>
media
>
core-updates
>
by-pkgid
>
6e2327ca1c896c6d674ae53117299f21
>
files
>
1448
