Skip to content
GitLab
Switch branch/tag
  1. 07 Apr, 2014 1 commit
    • Christian Schulte zu Berge's avatar
      Moved invalidation level from AbstractProperty to AbstractProcessor: · 293d43dd
      Christian Schulte zu Berge authored 
      To now, each property hat an _invalidationLevel field that was evaluated by processors when the property had changed in order to determine what has to be done. However, since properties could also be owned by other classes, this design was semantically misleading.
Therefore, it was removed with this commit and replaced by the invalidation map of each processor. Now, this per-processor mapping of property -> invalidation level is managed by the processor itself. Furthermore, the invalidation level is no longer setup during property creation but during AbstractProcessor::addProperty(), which also makes much more sense.

ATTENTION: Due to these intrusive API changes, the code of all processors and other classes handling properties needs to be changed. As a reminder, the implementation of addProperty() also now takes a reference instead of a pointer, so that old code does no longer compile.

refs #542
      293d43dd
  3. 05 Mar, 2014 1 commit
  5. 03 Mar, 2014 1 commit
  7. 02 Mar, 2014 1 commit
  9. 31 Jan, 2014 1 commit
  11. 14 Jan, 2014 2 commits
  13. 10 Jan, 2014 1 commit
  15. 08 Jan, 2014 1 commit
    • Christian Schulte zu Berge's avatar
      Refactoring AbstractProcessor::process() for clearer semantics and better and... · cd9d3feb
      Christian Schulte zu Berge authored 
      Refactoring AbstractProcessor::process() for clearer semantics and better and more uniform handling of invalidation levels:
 * AbstractProcessor::process() now calls updateShader(), updateProperties() and/or updateResult() with respect to the current invalidation level
 * each processor shall no longer override process() but the updateXYZ() methods, at minimum updateResult()
 * AbstractProcessor::process() takes care of (un)locking the processor itself (no need to do this from the outside anymore)

Further implicit changes:
 * Removed redundant HasPropertyCollection::updateProperties()
      cd9d3feb
  17. 29 Dec, 2013 1 commit
  19. 26 Dec, 2013 1 commit
  21. 24 Dec, 2013 2 commits
  23. 20 Dec, 2013 1 commit
  25. 19 Dec, 2013 3 commits
  27. 14 Dec, 2013 1 commit
  29. 13 Dec, 2013 2 commits
  31. 15 Oct, 2013 2 commits
  33. 08 Oct, 2013 2 commits
  35. 25 Sep, 2013 1 commit
    • Artur Grunau's avatar
      NumericProperty: provide a default step value · 8fcbfb5b
      Artur Grunau authored 
      Even though all integer-based properties derived from NumericProperty
used the same step value, T(1), it had to be specified when
instantiating them. To reduce boilerplate code in property
constructors, NumericProperty now uses T(1) as the default step value.
      8fcbfb5b
  37. 24 Sep, 2013 1 commit
    • Artur Grunau's avatar
      Update the typedefs of floating point properties · f318af5c
      Artur Grunau authored 
      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.
      f318af5c
  39. 21 Sep, 2013 1 commit
    • Artur Grunau's avatar
      Support setting the step of numeric properties · ec9a8b81
      Artur Grunau authored 
      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.
      ec9a8b81
  41. 17 Sep, 2013 1 commit
  43. 22 Jul, 2013 1 commit
  45. 17 Jul, 2013 1 commit
  47. 11 Jul, 2013 3 commits
  49. 09 May, 2013 1 commit
  51. 27 Apr, 2013 1 commit
  53. 14 Apr, 2013 1 commit
  55. 11 Apr, 2013 1 commit
  57. 15 Feb, 2013 1 commit
  59. 12 Feb, 2013 1 commit
  61. 10 Feb, 2013 1 commit