1. 15 Oct, 2013 1 commit
  2. 13 Oct, 2013 5 commits
    • Artur Grunau's avatar
      Fix bugs with the positioning of MDI windows · 1071efae
      Artur Grunau authored
      Previously, when an MDI window was being dragged very fast and its state
      changed from docked to floating (or vice versa), it wouldn't be placed
      under the cursor, but instead some way behind it (with regards to the
      drag direction). This happened because we decided where to place the
      window's based on its last position in its previous state. Now we use
      the cursor's position to calculate the window's new position, which
      fixes the problem.
      1071efae
    • Artur Grunau's avatar
      Refactor PipelineMdiSubWindow and rename it MdiDockedWindow · e3289b08
      Artur Grunau authored
      PipelineMdiSubWindow has been renamed MdiDockedWindow, and
      refactored to make it easier to use it with arbitrary widgets.
      e3289b08
    • Artur Grunau's avatar
      Store MDI-related classes under gui/mdi · 06a76302
      Artur Grunau authored
      To better group MDI-related classes, all of them have been moved to the
      ´gui/mdi´ directory.
      06a76302
    • Artur Grunau's avatar
      Refactor VisualizationPipelineWidget and rename it MdiFloatingWindow · b1df9da9
      Artur Grunau authored
      VisualizationPipelineWidget has been renamed MdiFloatingWindow, and
      refactored to make it easier to use it with arbitrary widgets.
      b1df9da9
    • Artur Grunau's avatar
      Refactor VisualizationPipelineWrapper and rename it MdiDockArea · 7e5e44b1
      Artur Grunau authored
      VisualizationPipelineWrapper has been renamed MdiDockArea, and refactored
      to make it easier to use it with arbitrary widgets. It now inherits from
      QMdiArea, which removes an unnecessary layer of indirection. Moreover, it
      creates MDI subwindows and floating windows only if necessary, i.e. when
      a widget stored in it changes state.
      7e5e44b1
  3. 11 Oct, 2013 4 commits
  4. 09 Oct, 2013 1 commit
  5. 08 Oct, 2013 10 commits
  6. 27 Sep, 2013 3 commits
  7. 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
  8. 24 Sep, 2013 4 commits
  9. 21 Sep, 2013 11 commits
    • 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
    • Artur Grunau's avatar
      Use IntAdjusterWidget in int and vector<int> property widgets · a3b78a9c
      Artur Grunau authored
      Previously, widgets for int and vector<int> properties used only spin
      boxes to display and let users modify the values of their associated
      property.
      
      Now that we have IntAdjusterWidget, IntPropertyWidget and all
      IVecPropertyWidgets have been updated to use it to make it possible to
      change the values of their components with not only a spin box, but also
      a slider.
      a3b78a9c
    • Artur Grunau's avatar
      IntAdjusterWidget: widget for modifying ints · 4dbd1800
      Artur Grunau authored
      IntAdjusterWidget displays and provides two ways of modifying integers:
      a slider that can be used to quickly change numeric values, and a spin
      box, which is better suited for precise adjustments.
      
      IntAdjusterWidget is a simple extension of AbstractAdjusterWidget<int>.
      It is designed to be used by IntPropertyWidget and widgets for vector
      properties storing integers.
      4dbd1800
    • Artur Grunau's avatar
      Derive DoubleAdjusterWidget from AbstractAdjusterWidget · edb7d691
      Artur Grunau authored
      DoubleAdjusterWidget used to inherit directly from QWidget. Rebasing it
      on top of AbstractAdjusterWidget<double>, however, greatly simplified
      its implementation and provided it with several additional API methods
      for free.
      edb7d691
    • Artur Grunau's avatar
      AbstractAdjusterWidget: base class for adjusters · 3a1f7c9f
      Artur Grunau authored
      AbstractAdjusterWidget is intended to be a base class for widgets
      combining a slider with a spin box. It abstracts common functionality of
      such widgets, leaving only signal/slot support and behaviour tweaks to
      be added in concrete adjuster classes.
      
      AbstractAdjusterWidget is a template class that can be parametrised with
      either double or int. Its API closely follows that of QSpinBox/QSlider.
      3a1f7c9f
    • Artur Grunau's avatar
      LogHighlighter: fix compilation errors with GCC · d8948a3f
      Artur Grunau authored
      Due to its language extensions, MSVC is more permissive than GCC with
      respect to C++ code that doesn't fully comply with the language
      standard. LogHighlighter relied on 2 such extensions: non-const rvalue
      references, and closing nested template argument lists with '>>'
      (instead of '> >'). Its code has now been fixed to conform to the
      standard, and compiles fine with GCC 4.7 as a result.
      d8948a3f
    • Artur Grunau's avatar
      Update property widgets in the GUI thread · 4f72e6fd
      Artur Grunau authored
      AbstractPropertyWidget's onPropertyChanged slot is invoked from non-GUI
      threads. Previously, it would call updateWidgetFromProperty directly,
      which resulted in Qt widgets being accessed from non-GUI threads. This
      in turn led to random crashes when properties were modified quickly and
      repeatedly from the GUI.
      
      Now we invoke updateWidgetFromProperty via a signal-slot connection with
      an internal signal, s_propertyChanged. This makes Qt take care of
      queueing slot accesses in the GUI thread for us.
      
      Fixes #36
      4f72e6fd
    • Artur Grunau's avatar
      Add support for boxed display of property widgets · 8b316f0c
      Artur Grunau authored
      Previously, property widgets have always had their components displayed
      horizontally next to a label with the property name. However, that made
      widgets consisting of many components (e.g. widgets for vector
      properties) hard to use because their components were squeezed together.
      
      Now AbstractPropertyWidget takes one additional optional argument,
      displayBoxed. If it's false, the widget is displayed as before. When
      it's true, the widget is laid out vertically in a QGroupBox. For now
      only widgets for vector properties set displayBoxed to true.
      8b316f0c
    • Artur Grunau's avatar
      Use DoubleAdjusterWidget in vector property widgets · e5e1bff3
      Artur Grunau authored
      Previously, widgets for double-valued vector properties used only spin
      boxes to display and let users modify the values of their associated
      property.
      
      Now that we have DoubleAdjusterWidget, vector property widgets have been
      updated to use it to make it possible to change the values of their
      components with not only a spin box, but also a slider.
      e5e1bff3
    • Artur Grunau's avatar
      FloatPropertyWidget: use DoubleAdjusterWidget · 77653ee0
      Artur Grunau authored
      Previously, FloatPropertyWidget used standard spin boxes and sliders to
      display and let users modify the value of its associated property.
      Consequently, it had to synchronise the states of those widgets on its
      own.
      
      Now that we have a separate widget that implements the two ways of
      changing double values that FloatPropertyWidget provides, it makes sense
      to simplify FloatPropertyWidget's code by making it use
      DoubleAdjusterWidget internally.
      77653ee0
    • Artur Grunau's avatar
      DoubleAdjusterWidget: widget modifying doubles · 778445ea
      Artur Grunau authored
      DoubleAdjusterWidget displays and provides two ways of modifying
      double-precision floating-point numbers: a slider that can be used to
      quickly change numeric values, and a spin box, which is better suited
      for precise adjustments.
      
      DoubleAdjusterWidget is designed to be used by FloatPropertyWidget and
      widgets for vector properties storing floats.
      778445ea