| Age | Commit message (Collapse) | Author |
|---|
|
|
|
|
|
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".
|
|
|
|
Update usages.
|
|
|
|
Note, it opens the config in read-write mode to check if it's
writable. This might present a race condition when config is
saved.
However, we're expecting all config saving to be done in the
user interface thread. Add a check for it however.
|
|
They're run from the UI thread so can even be interactive.
|
|
The generic QVariant comparison works badly for QList<QPointF>.
Create a comparator between two QVariants for base_value in value<tp>
ctor, using QVariant::value<tp> which returns right results once it's
converted to tp.
If a value was registered for a name in a bundle, use that comparator as
the comparator for that name. In case conflicting value types were
registered always use generic comparison for that name.
std::type_index needs to be used here since value<t> can be instantiated
in different modules (libraries), resulting in different value for the
comparator function pointer.
Move group::operator== to bundle type to avoid circular include for
connector.h.
Also use element_type more consistently in value<tp>.
|
|
The mapping window has 13 bundles total in use. Setting them all can take up
to a large fraction of a second on some windows filesystems. Do a single
config write instead.
|
|
- adjust usages
- add support for QList signals and metatype
|
