Enabling the switch on release builds will optimize the binaries as
normal, but will still include debug symbols. This is advantageous for
bugs that do not show up in debug builds without optimizations.
AppVeyor automatically updated to LLVM 8 while everything else was on 7.
It is not possible to downgrade to LLVM 7 on AppVeyor, so we'll update
everything else to LLVM 8.
The `QMessageLogContext` is only filled out in debug builds. Release
builds will have null pointers in `file` and `line`. This causes any
error attempted to be logged to result in a null pointer dereference.
Since we never use debug builds anyway, simply removing the uses of
`file` and `line` makes sense.
Github issue
https://github.com/OpenVR-Advanced-Settings/OpenVR-AdvancedSettings/issues/139
* Fix indentation in action manifest
* Rename action sets to drop unnecessary prefix notation
Since the variable is in the action_sets namespace it does not make
sense to prepend it with an identifier for it being constant, or a set.
* Rename input keys to drop prefix notation
The vars are in a namespace that only contains constant inputs, it
doesn't make sense to prepend it to every var.
* Rename actions to drop prefixes
It is implicit that actions are const values for sets, therefore the
prefix is not needed.
* Remove unneeded action set member func
* Move active action set in preparation for more action sets
* Move action strings above class
Class is not able to use variables in namespaces, which is stupid.
* Move sets into member variable
* Split music into separate action set
* Convert action_manifest.json to spaces only
* Refactor actions into separate action sets
* Rename main set to haptic
* Reorder action sets
The haptics and misc sets are misc bindings.
* format
* fixed manifest path issue
* Change path concat to use QDir
The old way was not platform independent.
* Move accessibility actions to motion set
* Remove "(Held)" from action name
Might be confusing for end users.
* Replace slash with platform independent separator
* Make paths output native paths
Them being in the overlay controller required them to be static, which
forces the compiler to give them a memory location at compile time. They
also don't really fit into the overlaycontroller.
Vasily
ykeara