| Age | Commit message (Collapse) | Author |
|---|
|
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
|
|
|
|
No visible changes (hopefully).
|
|
Adjust usages.
|
|
|
|
This is complicated by Qt's rejection of template classes.
Also move some stuff to slots where makes sense.
|
|
It's a shared_ptr<detail::bundle> stored in base_value.
|
|
|
|
Due to fucking AT&T vs BSD suit copyright defaults to all rights
reserved. Fuck Berne Convention as well.
|
|
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>.
|
|
They're now not cached in the singleton. Operations like "reload", "save", and
connector stuff short-circuit to prevent anything done with them
|
|
|
|
|
|
|
|
|
|
|
