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. 21 Jul, 2015 1 commit
  2. 20 Jul, 2015 1 commit
  3. 05 May, 2014 1 commit
  4. 13 Dec, 2013 1 commit
  5. 02 Nov, 2013 3 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
      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
  6. 15 Oct, 2013 1 commit
  7. 13 Oct, 2013 4 commits
  8. 21 Sep, 2013 2 commits
    • Artur Grunau's avatar
      Support dragging VP widgets back into the MDI area · f12ee2f7
      Artur Grunau authored
      VisualizationPipelineWidget and PipelineMdiSubwindow have been extended
      to report changes in their positions to VisualizationPipelineWrapper.
      Based on the information the latter receives, it decides when to undock
      MDI subwindows and dock floating pipeline widgets.
      
      As a result, it's now possible to drag visualization pipeline widgets
      back into the MDI area and turn them into MDI subwindows.
      f12ee2f7
    • Artur Grunau's avatar
      Handle dragging VP widgets out of the MDI area · 62373ebf
      Artur Grunau authored
      The way visualization pipelines are displayed has been considerably
      reworked. A new class, VisualizationPipelineWrapper, is now responsible
      for creating all necessary representations (VisualizationPipelineWidget,
      PipelineMdiSubwindow) of a visualization pipeline and seamlessly
      switching between them in response to the user's actions (window
      dragging, key presses, etc). As a result, it's now possible to drag
      visualization pipeline widgets out of the MDI area and turn them into
      top-level floating windows.
      62373ebf
  9. 15 Aug, 2013 1 commit
    • Artur Grunau's avatar
      DataNamePropertyWidget: fix null pointer deref · e28d6127
      Artur Grunau authored
      If a DataNamePropertyWidget is created for a DataNameProperty whose
      AccessInfo == READ, it doesn't instantiate a QLineEdit to display the
      property's value (QComboBox is used instead).
      
      Previously, the updateWidgetFromProperty method didn't check AccessInfo
      to see what display widget was in use, and simply always dereferenced
      the _lineEdit pointer. If AccessInfo == READ, it was null and the
      application crashed.
      
      Now updateWidgetFromProperty accesses only the combo box if
      AccessInfo == READ, and uses the line edit otherwise.
      
      Fixes #99
      e28d6127
  10. 15 Jul, 2013 1 commit
  11. 07 Feb, 2013 1 commit
  12. 02 Nov, 2012 1 commit
  13. 31 Oct, 2012 1 commit
  14. 26 Oct, 2012 1 commit
  15. 10 Aug, 2012 1 commit
  16. 03 Aug, 2012 1 commit