| Age | Commit message (Collapse) | Author |
|---|
|
Issue: #718
This allows for replacing the camera and point extractor code. See
`module.cpp' and `pt-api.hpp`.
|
|
|
|
|
|
|
|
|
|
It could cause microstutter.
|
|
|
|
It qualifies far less often now, but will likely reduce
jerkiness.
|
|
We heavily used "volatile bool" to check if the thread
loop should stop. But this functionality is already
provided by Qt5's QThread::requestInterruption.
In other cases, "volatile" is wonderfully
underspecified so it's better to ditch its usage in
favor of std::atomic<t>. At the time we don't appear to
be using the "volatile" keyword except when calling
win32's Interlocked*() family of functions as
necessary.
In freetrackclient's header the "volatile" qualifier
was used as part of a typedef. This doesn't work. Use
it as part of data declaration.
|
|
|
|
We allow for max of less than a pixel skew of all the points.
|
|
Also, changing "f" typedef to "float" won't break the build anymore.
|
|
- Pass `struct CamInfo' rather than several elements separately
- Reformat
- Return `struct CamInfo' together with the frame since then it's always valid
- Move the focal length formula into `struct CamInfo'
- Remove incorrect focal length formula rather than #if 0
- Pass some stuff by reference and not by pointer
|
|
- separate .{cpp,hpp} for few classes
- don't include namespaces globally; harmless but looks bad
anyway
- class with all public members to struct
|
|
We can't possibly have LEDs smaller than (6/3=2) each.
Especially not (2.5/6).
|
|
Use stack arrays rather than vectors. std::array may be a better
choice though.
|
|
|
|
With -D_USE_MATH_DEFINES MSVC defines the standard M_PI and
friends.
Since this preprocessor definition is now always passed as part
of the build system for MSVC. We can use M_PI as if on a
mission.
|
|
|
|
|
|
|
|
Adjust usages.
|
|
|
|
|
|
Issue: #386
|
|
|
|
|
|
We want double precision for POSIT. It's best for the type to be set in
ope place without the need to go over everything while switching it back
and forth during tests.
Machine epsilon for float is very small as per
<https://en.wikipedia.org/wiki/Machine_epsilon>. Also see the absurdly
high epsilon of 1e-4 of POSIT that we've had. With floats, making the
epsilon lower resulted in change deltas flushing to zero. This typically
led to the translation Z value being very unstable in PT.
After the epsilon and data type size changes the Z value is stable.
|
|
The input array has exactly 3 points. The vector has potentially more
points, sorted by circularity.
Spotted-by: @DaMichel
Closes #380
|
|
|
|
|
|
We use the cmath version to access the "float x" overload.
|
|
We no longer have this recurring problem since I enabled
ignoring executable bit changes on the Windows workstation.
|
|
|
|
causes breakage. even with denormal flush to zero it's not correct to
compare to epsilon.
|
|
This reverts commit a40a557caddad5285bd03b79dca5f7a94d1f44c5.
|
|
|
|
|
|
|
|
Closes #224
|
