1. 13 Dec, 2013 1 commit
  2. 12 Dec, 2013 1 commit
  3. 06 Dec, 2013 1 commit
  4. 05 Dec, 2013 1 commit
  5. 28 Nov, 2013 2 commits
  6. 30 Oct, 2013 1 commit
  7. 28 Oct, 2013 1 commit
  8. 25 Oct, 2013 1 commit
  9. 15 Oct, 2013 2 commits
  10. 11 Oct, 2013 2 commits
  11. 09 Oct, 2013 1 commit
  12. 08 Oct, 2013 8 commits
  13. 27 Sep, 2013 2 commits
  14. 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
  15. 24 Sep, 2013 3 commits
  16. 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
  17. 18 Sep, 2013 1 commit
  18. 17 Sep, 2013 1 commit
  19. 04 Sep, 2013 2 commits
  20. 03 Sep, 2013 1 commit
  21. 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
  22. 19 Aug, 2013 1 commit
  23. 22 Jul, 2013 1 commit
  24. 16 Jul, 2013 1 commit