| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
|
|
The settings need a proper save/load mechanism to operate.
|
|
|
|
Use more C++17 features where this helps any.
|
|
- 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.
|
|
Adjust usages.
|
|
|
|
|
|
- Received values got converted to integers. I find
this hard to believe. Even if this is so, converting
to double leaves forward-compatibility if the sender
software gets its act together.
- There was a buffer overflow when indexing the
"indices" array.
- Mutex scope bigger than necessary.
The code is copy-pasted from the FreePIE tracker.
Perhaps if its own code was easier to understand, there
wouldn't be any buffer overflows to begin with.
|
|
|
|
- need use QThread::exit to stop the event loop
- QObject::moveToThread works when passed a working
thread
- stop QTimer in its thread
|
|
|
|
Related-to: #650
|
|
Related-to: #650
|
|
|
|
|
