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 2 commits
    • Christian Schulte zu Berge's avatar
      Completed refactoring campvis-application package: · dfec0e89
      Christian Schulte zu Berge authored
      All classes in campvis-application now have the CAMPVIS_APPLICATION_API macro specifying dll export/import state. The executable is now called campvis-gui.
      dfec0e89
    • Christian Schulte zu Berge's avatar
      Started working on fancy scripting support: · 38884324
      Christian Schulte zu Berge authored
      * Split up campvis-application executable into campvis-application library and campvis executable. This allows to create a Lua module for the stuff in campvis-application.
      * Added Lua binding stub for campvis-application
      * Revised LuaTable and it's offsprings to (almost) fully model the Lua table model
      * Added MetatableLuaTable to model Lua's metatables
      * LuaTable supports caching the current field state in a value map supporting lazy instantiation
      * Added LuaTableTreeModel transforming the LuaTable structure into a QAbstractItemModel
      * Extended ScriptingWidget to contain both a LuaTableTreeWidget containing a variable view as well as with a LuaCompleter automatically completing the typed Lua commands with the variables extracted from the lua state.
      
      refs #643
      38884324
  2. 20 Jul, 2015 1 commit
  3. 14 Dec, 2014 1 commit
  4. 10 Dec, 2014 1 commit
  5. 24 Nov, 2014 1 commit
  6. 29 Oct, 2014 3 commits
  7. 30 Sep, 2014 1 commit
  8. 27 Jul, 2014 1 commit
    • Christian Schulte zu Berge's avatar
      Introducing sigslot::concurrent_pointer_list<T> a list-like container allowing... · 8671e65c
      Christian Schulte zu Berge authored
      Introducing sigslot::concurrent_pointer_list<T> a list-like container allowing thread-safe bidirectional iteration, insertion and removal of elements. Single constraint is that the element type must be a pointer type (or at least have pointer semantics) and never be 0. This is neat, as this class offers exactly what we need for a lock-free sigslot implementation.
      
      Updated sigslot implementation to use concurrent_pointer_list for connection storage. Hence, we can get rid of the locking mechanisms, which got completely removed.
      
      Since this simplified template definitions for sigslot, many campvis files needed to be adapted (i.e. removing the <> from has_slots<> and signal0<>).
      
      refs #384
      
      Conflicts:
      	core/classification/genericgeometrytransferfunction.h
      	core/eventhandlers/trackballnavigationeventlistener.h
      	core/pipeline/processordecoratormasking.h
      	core/properties/propertycollection.h
      	core/properties/transferfunctionproperty.h
      	core/tools/opengljobprocessor.h
      8671e65c
  9. 05 May, 2014 1 commit
  10. 04 Apr, 2014 1 commit
  11. 13 Dec, 2013 1 commit
  12. 15 Oct, 2013 1 commit
  13. 21 Sep, 2013 2 commits
    • 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
  14. 06 Feb, 2013 1 commit
  15. 30 Jan, 2013 1 commit
  16. 02 Nov, 2012 1 commit
  17. 31 Oct, 2012 1 commit
  18. 26 Oct, 2012 1 commit
  19. 10 Aug, 2012 1 commit
  20. 06 Aug, 2012 2 commits
  21. 03 Aug, 2012 1 commit