GitLab

FloatPropertyWidget and VecPropertyWidget configure their adjusters to
display as many decimals as their properties have significant decimal
places. Moreover, they connect to the s_decimalsChanged signal in order
to reconfigure their adjusters when the number of significant decimal
places of their properties changes.

Floating point properties were previously typedef'd to specific
instantiations of NumericProperty. Now that we have
FloatingPointProperty, which extends NumericProperty to control how many
decimal places should be shown when displaying the property's value, all
typedefs for floating point properties have been updated to point to it
instead.

As a result, many processors and pipelines needed to have their includes
and/or constructors fixed to import and work with the new typedefs.

A new attribute has been added to all numeric properties: step value. It
determines the value of a single increment/decrement that numeric
property widgets use when their associated properties are modified using
sliders or spin boxes (users are still able to type any valid property
value in text edits).

Numerous processors and pipelines had to be updated to work with the
changed NumericProperty interface. However, choosing a well-suited step
value for each property can make it easier for users to modify the
property — using one step value for all properties leads to cases where
it is either too small, causing users to go through property values
which don't cause any visible change, or too big, making it difficult to
quickly determine the right property value.

DoubleAdjusterWidget used to inherit directly from QWidget. Rebasing it
on top of AbstractAdjusterWidget<double>, however, greatly simplified
its implementation and provided it with several additional API methods
for free.

AbstractPropertyWidget's onPropertyChanged slot is invoked from non-GUI
threads. Previously, it would call updateWidgetFromProperty directly,
which resulted in Qt widgets being accessed from non-GUI threads. This
in turn led to random crashes when properties were modified quickly and
repeatedly from the GUI.

Now we invoke updateWidgetFromProperty via a signal-slot connection with
an internal signal, s_propertyChanged. This makes Qt take care of
queueing slot accesses in the GUI thread for us.

Fixes #36

Previously, property widgets have always had their components displayed
horizontally next to a label with the property name. However, that made
widgets consisting of many components (e.g. widgets for vector
properties) hard to use because their components were squeezed together.

Now AbstractPropertyWidget takes one additional optional argument,
displayBoxed. If it's false, the widget is displayed as before. When
it's true, the widget is laid out vertically in a QGroupBox. For now
only widgets for vector properties set displayBoxed to true.

Previously, widgets for double-valued vector properties used only spin
boxes to display and let users modify the values of their associated
property.

Now that we have DoubleAdjusterWidget, vector property widgets have been
updated to use it to make it possible to change the values of their
components with not only a spin box, but also a slider.

Previously, FloatPropertyWidget used standard spin boxes and sliders to
display and let users modify the value of its associated property.
Consequently, it had to synchronise the states of those widgets on its
own.

Now that we have a separate widget that implements the two ways of
changing double values that FloatPropertyWidget provides, it makes sense
to simplify FloatPropertyWidget's code by making it use
DoubleAdjusterWidget internally.

Each FloatPropertyWidget now gives the user two ways of modifying its
underlying property's value: the slider can be used for quick changes,
the spin box — for precise adjustments.

git-svn-id: https://camplinux.in.tum.de/svn/campvis/trunk@429 bb408c1c-ae56-11e1-83d9-df6b3e0c105e

git-svn-id: https://camplinux.in.tum.de/svn/campvis/trunk@338 bb408c1c-ae56-11e1-83d9-df6b3e0c105e

git-svn-id: https://camplinux.in.tum.de/svn/campvis/trunk@335 bb408c1c-ae56-11e1-83d9-df6b3e0c105e

git-svn-id: https://camplinux.in.tum.de/svn/campvis/trunk@326 bb408c1c-ae56-11e1-83d9-df6b3e0c105e

git-svn-id: https://camplinux.in.tum.de/svn/campvis/trunk@280 bb408c1c-ae56-11e1-83d9-df6b3e0c105e

 * added update_legal_header.py script for updating the legal header in all code files of the project
 * ran the file => all TUMVis source files now contain the legal header

git-svn-id: https://camplinux.in.tum.de/svn/campvis/trunk@231 bb408c1c-ae56-11e1-83d9-df6b3e0c105e

git-svn-id: https://camplinux.in.tum.de/svn/campvis/trunk@222 bb408c1c-ae56-11e1-83d9-df6b3e0c105e

* added DataHandle::removeData
* include/forward declaration clean-up

git-svn-id: https://camplinux.in.tum.de/svn/campvis/trunk@208 bb408c1c-ae56-11e1-83d9-df6b3e0c105e