* add delay if interface not found
* adjust initialization behavior
* pushed for debugging reasons for concerned parties
* comment out simple recenter
* remove old style motion, some minor optimizations
* optimize default case check
* optimized default condition
* change manifest install behavior to trigger on desktop mode as well
* add desktop mode binding launch
* add tracker overlay option to utils
* commit to check status
* attempt to fix native LH issues with chaperone when exiting
* add desktop mode toggle and some cleanup
* remove adjust chaperone
* remove clang format from ci, increment version, cleanup
* update circle ci
* fix conversion warning
* add F13-19 to keyboard parser
* add additional logging around failure to initialize
* add unsaved changes
* update version 5.8.1
* fix some collisions in enum declaration
* add controller powers on steamvr, and no HMD to steamvr tab, increment version
* slightly alter drag movement, fix qml issue
* code cleanup
* fix logspam/attempt to delete non existant overlays
* increment version 5.8.3
The implementation is simple 3D vector scaling and addition. The
HmdMatrix34_t consists of a 3x3 rotation matrix and a 3D vector for
position.
The overlay position is only updated whenever a new overlay is changed
because we need the old overlay position in order to modify it. The
openvr call to get the position is only updated whenever you open the
menu.
A new page was created due to lack of space on the utilities page.
Elements work like they've always done, this just moves the commonly
used components away from the global namespace.
The qmldir file still does something, although at this point it is
unknown exactly how it's used and whether or not it could be changed to
simplify imports across the block.
This removes the massively indented logic in the previous version.
Notice that individual components will still be imported with an
import "utilities_page". Therefore anything except UtilitiesPage.qml
should be in a separate folder.
The QML at the moment is a giant mess. Moving pages into individual
folders and properly abstracting the sub components of the pages will
allow for much easier development and better error messages.
Additionally it will prevent polluting the global namespace. Really, all
the reasons for avoiding globally available values and using
abstractions in regular programming also come into play here.
ykeara
Vasily