Skip to content

GitLab

Switch branch/tag
  1. 13 Oct, 2014 1 commit
  3. 09 Oct, 2014 1 commit
  5. 27 Jul, 2014 1 commit
    • Christian Schulte zu Berge's avatar
      Streamlined AbstractProcessor API: · 36ab435a
      Christian Schulte zu Berge authored 
      INVALID_RESULT, INVALID_PROPERTIES, INVALID_SHADER is validated automatically by AbstractProcessor::process(). Hence, there is finally no need anymore to validate these three different levels in each processor.
      36ab435a
  7. 05 May, 2014 1 commit
  9. 22 Apr, 2014 1 commit
  11. 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
  13. 04 Apr, 2014 1 commit
  15. 13 Jan, 2014 1 commit
  17. 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
  19. 13 Dec, 2013 1 commit
  21. 28 Nov, 2013 1 commit
  23. 17 Nov, 2013 1 commit
  25. 30 Oct, 2013 2 commits
  27. 29 Oct, 2013 1 commit
  29. 28 Oct, 2013 1 commit
  31. 15 Oct, 2013 1 commit
  33. 14 Oct, 2013 1 commit
  35. 11 Oct, 2013 1 commit
  37. 08 Oct, 2013 1 commit
  39. 25 Sep, 2013 1 commit
    • Artur Grunau's avatar
      FloatingPointProperty: provide a default step value · 4853ed7d
      Artur Grunau authored 
      Even though many float-based properties derived from
FloatingPointProperty used the same step value, T(0.01), it had to be
specified when instantiating them. To reduce boilerplate code in
property constructors, FloatingPointProperty now uses T(0.01) as the
default step value.
      4853ed7d
  41. 24 Sep, 2013 1 commit
  43. 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
  45. 04 Sep, 2013 1 commit
  47. 29 Aug, 2013 1 commit
    • Christian Schulte zu Berge's avatar
      Branching work to introduce new FBO handling concept: · 42480c65
      Christian Schulte zu Berge authored 
       * each VisualizationProcessor manages its own FBO
 * instead of creating a whole new FBO each process(), the processors shall only create and attach textures to the FBO
 * the FramebufferActivationGuard offers automatic (de)activation and detachment of all textures

SimpleRaycaster already uses the new concept, the rest still uses the legacy API
      42480c65
  49. 19 Aug, 2013 1 commit
  51. 16 Jul, 2013 1 commit
  53. 14 May, 2013 1 commit
  55. 12 Feb, 2013 1 commit
  57. 10 Feb, 2013 1 commit
  59. 18 Jan, 2013 1 commit
  61. 12 Nov, 2012 1 commit
  63. 08 Nov, 2012 1 commit
  65. 04 Nov, 2012 1 commit
  67. 02 Nov, 2012 2 commits
  69. 31 Oct, 2012 1 commit
  71. 26 Oct, 2012 1 commit
  73. 21 Sep, 2012 1 commit
  75. 15 Sep, 2012 1 commit