aboutsummaryrefslogtreecommitdiffstats
path: root/plugin/cursornavigationattached.h
Commit message (Collapse)AuthorAgeFilesLines
* add possibility to add offset to the directional movement of the cursorBramastyo Harimukti2019-11-271-0/+6
| | | | | Change-Id: I79d33e3f944fcdd89023dbc84534318392bfee60 Reviewed-by: Egor Nemtsev <enemtsev@luxoft.com>
* fix build against Qt 5.14Grigorii Zimin2019-11-271-3/+4
| | | | | Change-Id: I882e79ebaf371eb6fb4bb6bc163b0b9099b370bc Reviewed-by: Egor Nemtsev <enemtsev@luxoft.com>
* Add currentItem -methodAntti Hölttä2019-08-021-1/+3
| | | | | | | | Add currentItem -method to the attached CursorNavigation property. The method returns the QQuickItem that currently has the cursor. Change-Id: I3b43f819d915280bfab58639ccfb429fdcf818a4 Reviewed-by: Robert Griebl <robert.griebl@pelagicore.com>
* Add license and copyright informationAntti Hölttä2019-03-191-0/+39
|
* Add existing isues as TODOsAntti Hölttä2019-03-181-0/+1
|
* Start tests, basic case pretty completeAntti Hölttä2019-03-181-4/+1
|
* Add redirect feature for manually fine tuning the cursor's movementAntti Hölttä2019-03-181-1/+11
| | | | | | | | Cursornavigation now has a property redirects, that allows defining exceptions to the navigation behaviour. A redirect allows defining a starting and an ending angle and a target object. If the move command's direction falls between the limits, the algorithm is bypassed and cursor is moved to the target object.
* Add callbacks for magnitude, moves and actionsAntti Hölttä2019-03-181-2/+19
| | | | | | | | | When cursor is moved, the current item is informed of the actions via callbacks. Eg. when cursor is moved up, the item that had the cursor will have its movedUp signal fired. It is now also possible to inform navigable items over incomplete movement, or the magnitude of the movement. This may be used eg. to make buttons or elements to flip/rotate to indicate that the cursor is about to be moved.
* Add available-function for a cursor navigableAntti Hölttä2019-03-181-1/+6
| | | | | | Availability means that the item first of all accepting cursor, visible, enabled, and within its parent's geometry. This value is meant for the algorithms to define if item is navigable.
* Add find-functionAntti Hölttä2019-03-181-0/+5
| | | | | | find-function is similar to the move, but instead of moving the cursor, it returns the item that cursor would move to if move was called with the same arguments
* Add 360 algorithmAntti Hölttä2019-03-181-1/+2
| | | | | Add algorithm that allows navigation to any direction. Works somewhat well now. Example app has a page with a gamepad/stick support.
* CursorNavigationAttached now implements the control interfaceAntti Hölttä2019-03-181-0/+11
| | | | | | CursorNavigationAttached now implements the functions for moving the cursor and for giving commands. This makes it possible to reassign the control keys, or use other input sources as well
* More on scopes, works to some extent in the test programAntti Hölttä2019-03-181-5/+12
| | | | | Scope may be entered and escaped. Navigable items may have escape targets defined
* Refactor item registration with scopes in mindAntti Hölttä2019-03-181-5/+13
| | | | | ItemRegister class removed and items now keep track of their own cursor navigable child items. Navigation happens now only between siblings.
* Initial commit, demoable pocAntti Hölttä2019-03-181-0/+54
Sort of working with 4 dir navigation, check demoapp