1. 15 Oct, 2013 1 commit
  2. 25 Sep, 2013 2 commits
    • 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.
    • Artur Grunau's avatar
      NumericProperty: use step size in de- and increment() · b625ea64
      Artur Grunau authored
      Numeric properties were previously incremented and decremented by 1 cast
      to the property's underlying type, e.g. tgt::vec2(1). That worked fine
      for integer-based properties, but those storing floating-point numbers
      could benefit from using the step value in decrement() and increment().
      Now that's exactly how NumericProperty behaves.
  3. 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
      As a result, many processors and pipelines needed to have their includes
      and/or constructors fixed to import and work with the new typedefs.
  4. 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.
  5. 16 Aug, 2013 1 commit
  6. 21 Jun, 2013 1 commit
  7. 09 May, 2013 1 commit
  8. 10 Feb, 2013 1 commit
  9. 05 Feb, 2013 1 commit
  10. 11 Jan, 2013 1 commit
  11. 02 Nov, 2012 1 commit
  12. 31 Oct, 2012 1 commit
  13. 26 Oct, 2012 1 commit
  14. 06 Sep, 2012 1 commit
  15. 03 Sep, 2012 1 commit
  16. 10 Aug, 2012 1 commit
  17. 06 Aug, 2012 1 commit
  18. 03 Aug, 2012 1 commit
  19. 19 Jul, 2012 1 commit
  20. 18 Jul, 2012 1 commit