Age | Commit message (Collapse) | Author |
|
- 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.
|
|
Fix few of the inspection warnings from CLion that
make any sense at all.
|
|
|
|
Spotted by: @cpuwolf
Issue: #718
|
|
|
|
Adjust usages.
|
|
Issue: #718
This allows for replacing the camera and point extractor code. See
`module.cpp' and `pt-api.hpp`.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
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.
|
|
Adjust usages.
There are ODR issues with MSVC and it doesn't support
C++17 "static inline constexpr" _variables_. Otherwise,
"signal_fun" could be a variable and not a function.
The usages in accela/ewma2 dialog are more verbose now
but the original API was silly.
|
|
- fix a braino (don't divide by two)
- default to exact averaging, not perceptual weighted
- use more specific cv::addWeighted
|
|
|
|
|
|
|
|
|
|
Profiling over a longer time period showed a bottleneck
while iterating pixels with `cv::floodFill()'. Contours
are actually faster, and we have MeanShift to establish
the proper center basing on pixel intensities.
|
|
It mostly works from my testing.
|
|
|
|
- move dt handling here, from ITracker impl
- don't depend on other PT headers. we'd like to reuse the code.
- adjust return value convention.
- get rid of dt_valid
- return fps as a double
Adjust usages in ITracker impl and dialog.
|
|
|
|
|
|
|
|
|
|
|
|
Also simplify timer logic.
|
|
Use stack arrays rather than vectors. std::array may be a better
choice though.
|
|
We've had two reported crashes.
Issue: #468
|
|
Suggested-by: MathijsG
Issue: #454
|
|
|
|
It's broken and users complain on the issue tracker.
Also fix tab stops.
|
|
- change button text to "stop calibration" and "start calibration"
respectively.
- gray out the values while calibration is running
- run calibration at 10 Hz on a separate timer from dialog update
Issue: #416
|
|
Adjust usages.
|
|
|
|
|
|
In particular PT's calibration interval was 10 Hz which is too much by
far. Make both 4 Hz.
Issue: #344
|
|
|
|
Closes #224
|