2.12.2021, 9:00 - 11:00: Due to updates GitLab may be unavailable for some minutes between 09:00 and 11:00.

  1. 13 Jan, 2014 2 commits
    • Christian Schulte zu Berge's avatar
      * Updated VolumeRenderer and VolumeExplorer to use user-defined RaycastingProcessor · 8d26da04
      Christian Schulte zu Berge authored
      * RaycastingProcessor now has the p_targetImageID property and optionally uses a custom GLSL version for the shader
      * Introducing PropertyCollection::getNestedProperty allowing to get nested properties with a single method call
      * Fixed StringUtils::split() methods being broken with multi-character delimiters
      8d26da04
    • Christian Schulte zu Berge's avatar
      Fixing commit 5f72759e: · 56724724
      Christian Schulte zu Berge authored
      C++ implicit conversion rules made ShaderManager::loadSeparate() ambiguous in some cases. So I decided to cut loose ends and completely refactored loading with standard version into ShaderManager::load() and loading with custom version into ShaderManager::loadWithCustomGlslVersion().
      ShaderManager::loadSeparate() is no longer available!
      56724724
  2. 12 Jan, 2014 1 commit
  3. 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
  4. 05 Jan, 2014 1 commit
  5. 04 Jan, 2014 1 commit
  6. 13 Dec, 2013 1 commit
  7. 12 Dec, 2013 1 commit
  8. 06 Dec, 2013 1 commit
  9. 05 Dec, 2013 1 commit
  10. 28 Nov, 2013 2 commits
  11. 30 Oct, 2013 1 commit
  12. 28 Oct, 2013 1 commit
  13. 25 Oct, 2013 1 commit
  14. 15 Oct, 2013 2 commits
  15. 11 Oct, 2013 2 commits
  16. 09 Oct, 2013 1 commit
  17. 08 Oct, 2013 8 commits
  18. 27 Sep, 2013 2 commits
  19. 25 Sep, 2013 3 commits
    • Christian Schulte zu Berge's avatar
      Revised LQ mode concept for visualization pipelines/processors: · b3913e3d
      Christian Schulte zu Berge authored
      Instead of having the LQ mode tied to the pipeline, each VisualizationProcessor has now a lqMode property effectively halfsampling the viewport size. The TrackballNavigationEventHandler was adapted to these changes and thus simplified.
      b3913e3d
    • 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
    • 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
  20. 24 Sep, 2013 3 commits
  21. 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
  22. 18 Sep, 2013 1 commit
  23. 17 Sep, 2013 1 commit
  24. 04 Sep, 2013 1 commit