| Age | Commit message (Collapse) | Author |
|---|
|
Using int as `stored_type' for bool made Qt signals not
work. Evident when ticking the "asymmetric mapping"
checkboxes in the mapping window.
Remove some std::decay_t usage, there's no need for
either decay or remove_cvref.
In `value<t>::get()', `bundle::get_variant' of an
undefined key will fall back to `return def' so remove
the duplicate logic.
|
|
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
|
|
|
|
Adjust usages.
|
|
|
|
|
|
- mapping window clamps are now value<max_clamp> in
spline
- clamp won't mess up saved spline content
- clean up artifacts on spline widget
|
|
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.
|
|
That made sliders from 2.3.7 still incompatible.
Apparently QVariant cares a lot about the difference
between "options::slider_value",
"::options::slider_value", and "slider_value".
|
|
|
|
Also combine the traits classes and make them more useful.
|
