| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Maybe global `-Wcomma' is too harsh.
There should be no functional changes whatsoever.
|
|
No functional changes.
- add `override' everywhere where missing
- almost pass clang's `-Wweak-vtables'
- avoid some float/double conversions
- remove unused private members
- make signedness conversions explicit
- put stuff in right namespaces to aid analysis
|
|
Rename traits' functions to be more explicit.
Most of the changes are pretty old and I can't read
them at this time, sorry.
Adjust usages.
Issue: #825
Reported-by: @DanielKinsman
|
|
|
|
1. Calling valueChanged didn't invoke machinery in
value<t>, only base_value aka value_.
There's a fast path in value<t>::type() despite the
pessimization.
2. Split global scope stuff into options::globals from
the options::globals stuff
3. Adjust usages
|
|
|
|
|
|
No visible changes (hopefully).
|
|
|
|
Use more C++17 features where this helps any.
|
|
Spotted-by: @zanoni-mbdyn
|
|
Now that we translate module names, they have to be
stored as language-neutral in the config.
- add tie_setting overload with from/to conversions
- add logic to opentrack/main-window
- add migration
- remove actually useless tie_setting_traits
|
|
Otherwise we get QCoreApplication used before
QApplication instance is created.
Requesting the sorted migration data will force the
thunks.
|
|
- use `static constexpr inline' to avoid requiring
explicit declarations in object code
- use `const Foo* const' to maybe put into readonly
binary segment (at least for ELF DSOs)
- `constexpr' in function scope has storage, avoid
`static'
- don't use `constexpr' where there's no advantage,
like arrays
We'd like to avoid overhead of atomic initialization
for each function call. No idea how `static constexpr'
requiring storage in the standard plays with atomic
initialization requirement. Hearsay points that
`constexpr' without `static' in block scope behaves
more to our liking. It's all hazy though.
I'm not 100% sure if `static inline constexpr' has any
storage. Hopefully none, like a #define, and stuff
bigger than registers gets coalesced within the same
module, with small stuff being immediates.
|
|
cf. #746
|
|
|
|
Don't include current settings headers. Once they change the old
migration needs rewriting. Rewrite it now and make it a point not to
include current headers.
The old Accela migration is pointless given that settings changed max
values.
|
|
Relative translation mode now has three states:
- disabled
- always enabled
- enabled when not aiming
In the third mode, looking very close to center disables reltrans. The
exact values aren't final.
|
|
Adjust usages.
|
|
|
|
Prevent common characters from breaking the saved list. Use unprintable
characters. Add migration.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
It's only the tie_setting(slider_value, QSlider) that
has race-free slider updates. Needed to update the
threshold slider representation.
Remove the tie_setting(int, QSlider) overload since it
doesn't have the logic.
Add a migration.
Add base_value::notify() for use-cases like the
checkbox updating the label.
|
|
|
|
Update usages.
|
|
Issue: #571
|
|
|
|
Adjust usages.
|
|
It's not annoying having to type it anymore. Also
"otr_boilerplate" -> "otr_module".
|
|
|
|
Polish speakers typically know English well enough and translations are
awkward.
|
|
|
|
My eyes bleed a bit less
|
|
clang whines on the initial hack
|
|
|
|
thread_local is expensive.
|
|
|
