Currently job artifacts in CI/CD pipelines on LRZ GitLab never expire. Starting from Wed 26.1.2022 the default expiration time will be 30 days (GitLab default). Currently existing artifacts in already completed jobs will not be affected by the change. The latest artifacts for all jobs in the latest successful pipelines will be kept. More information: https://gitlab.lrz.de/help/user/admin_area/settings/continuous_integration.html#default-artifacts-expiration

  1. 02 Nov, 2013 5 commits
    • Artur Grunau's avatar
      MdiDockableWindow: new MDI helper class · 6d4262de
      Artur Grunau authored
      MdiDockableWindow has been extracted from MdiDockArea to simplify and
      better structure our MDI implementation. The new class takes care of
      creating all necessary representations (docked and floating window) of
      widgets added to MdiDockArea and seamlessly switching between them in
      response to the user's actions (window dragging, key presses, etc).
      
      MdiDockableWindow improves our MDI implementation in two ways:
      - MdiFloatingWindow and MdiDockedWindow instances shouldn't be
        interacted with directly; they're created and disposed of as needed,
        and therefore can't be used as a handle to access and modify an MDI
        window's state; MdiDockableWindow, in contrast, fits this role
        perfectly; it manages both representations of an MDI window, and as
        a result stays around as long as at least one of them is needed
      - managing state transitions of many sub-windows directly in MdiDockArea
        was becoming clumsy as signal mapping and dynamic properties were
        required; having a separate widget that only has to control the state
        of one sub-window makes the code related to state transitions much
        simpler
      6d4262de
    • Artur Grunau's avatar
      Properly hide docked MDI subwindows that got closed · 8126df4d
      Artur Grunau authored
      Closing a docked MDI subwindow caused it to disappear if the MDI area
      was in SubWindowView mode, but its inactive tab could still be seen in
      TabbedView mode.
      
      If a docked MDI subwindow gets closed, hide it by removing it from the
      MDI area.
      8126df4d
    • Artur Grunau's avatar
      Add a "Tools" submenu to the main menu · dd068eea
      Artur Grunau authored
      The "Tools" submenu lists all standard docked tools offered by the
      application (i.e. "Pipeline tree", "Pipeline properties", and "Log
      viewer"), and lets the user toggle their visibility.
      dd068eea
    • Artur Grunau's avatar
      Initial implementation of a main menu · c8ef752b
      Artur Grunau authored
      This commit adds a simple main menu to the application. For the time being
      it only has 2 submenus, "File" and "Visualizations". The latter is created
      by MdiDockArea and lets users manage the visibility and placement of
      canvas windows.
      c8ef752b
    • Artur Grunau's avatar
      348c710e
  2. 26 Oct, 2013 1 commit
    • Artur Grunau's avatar
      Fix a double free in LogHighlighter's destructor · 88d2e9a1
      Artur Grunau authored
      In its destructor, LogHighlighter first of all deleted its filter regex
      explicitly, and then called `setFilterRegExp(0)`, triggering a second —
      this time somewhat implicit — delete. If the filter regex pointer was
      not NULL, this caused the application to crash due to a double-free.
      
      Fix this error by not invoking `setFilterRegExp` in LogHighlighter's
      destructor; the explicit delete performs the same cleanup as
      `setFilterRegExp` anyways.
      88d2e9a1
  3. 25 Oct, 2013 1 commit
  4. 16 Oct, 2013 1 commit
  5. 15 Oct, 2013 3 commits
  6. 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
  7. 11 Oct, 2013 4 commits
  8. 09 Oct, 2013 1 commit
  9. 08 Oct, 2013 10 commits
  10. 27 Sep, 2013 3 commits
  11. 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
  12. 24 Sep, 2013 4 commits
  13. 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