Jean-Christophe Fillion-Robin

Open question: Should libvcs depends on package like svn, GitPython or python-hglib

2

There are already few packages specialized in handling interaction with these repository: - https://pypi.python.org/pypi/svn - https://pypi.python.org/pypi/GitPython/ - https://pypi.python.org/pypi/python-hglib I wonder if libvcs should make use of them ? It is...

Exporting two segmentation nodes in a row in the same output directory overwrite the prevous one

2

Since the DICOM file name is initialized using the current date and time, exporting in the same directory overwrites the previous file. https://github.com/QIICR/QuantitativeReporting/blob/87852c8460ed54de70e8c838f16ddf62da539546/DICOMPlugins/DICOMSegmentationPlugin.py#L351 https://github.com/QIICR/QuantitativeReporting/blob/87852c8460ed54de70e8c838f16ddf62da539546/DICOMPlugins/DICOMSegmentationPlugin.py#L437-L440

Fix py_QuantitativeReportingTests

3

$ ctest -V ``` Start 1: py_QuantitativeReportingTests 1: Test command: /home/kitware/Dashboards/Nightly/Slicer-0-build/Slicer-build/Slicer "--no-splash" "--testing" "--launcher-additional-settings" "/home/kitware/Dashboards/Nightly/S-0-E-b/QuantitativeReporting-build/AdditionalLauncherSettings.ini" "--additional-module-paths" "/home/kitware/Dashboards/Nightly/S-0-E-b/QuantitativeReporting-build/lib/Slicer-4.9/qt-scripted-modules" "/home/kitware/Dashboards/Nightly/S-0-E-b/SlicerDevelopmentToolbox-build/./lib/Slicer-4.9/qt-loadable-modules" "/home/kitware/Dashboards/Nightly/S-0-E-b/SlicerDevelopmentToolbox-build/./lib/Slicer-4.9/cli-modules" "/home/kitware/Dashboards/Nightly/S-0-E-b/PETDICOMExtension-build/./lib/Slicer-4.9/qt-loadable-modules" "/home/kitware/Dashboards/Nightly/S-0-E-b/PETDICOMExtension-build/./lib/Slicer-4.9/cli-modules" "/home/kitware/Dashboards/Nightly/S-0-E-b/DCMQI-build/dcmqi-build/dcmqi-build/bin" "/home/kitware/Dashboards/Nightly/S-0-E-b/SlicerDevelopmentToolbox-build/./lib/Slicer-4.9/qt-scripted-modules" "--additional-module-paths" "/home/kitware/Dashboards/Nightly/S-0-E-b/QuantitativeReporting-build/lib/Slicer-4.9/qt-scripted-modules" "/home/kitware/Dashboards/Nightly/S-0-E-b/QuantitativeReporting-build/lib/Slicer-4.9/cli-modules" "/home/kitware/Dashboards/Nightly/S-0-E-b/QuantitativeReporting-build/lib/Slicer-4.9/qt-loadable-modules" "--python-code" "import slicer.testing;...

Update script to support building Qt 5.15.x on Ventura and above

1

Related notes: * https://discourse.slicer.org/t/transition-of-macos-preview-build-from-host-10-13-high-sierra-to-13-ventura/28668 * https://github.com/Slicer/DashboardScripts/pull/53#issuecomment-1384355365 cc: @jamesobutler

As described in [QTBUG-89364](https://bugreports.qt.io/browse/QTBUG-89364), specifying `-no-xinerama` does not work. A patch have been provided in the referenced issue. Since described tradeoff seems reasonable, we should consider applying the patch and...

See: - https://github.com/Kitware/fletch/blob/master/CMake/External_Qt.cmake - https://gitlab.kitware.com/ben.boeckel/common-superbuild/tree/superbuild-revamp/standalone-qt

The idea would be to edit [build_qt_with_openssl.cmake](https://github.com/jcfr/qt-easy-build/blob/e03358423dab3368910fdfdd75ba4862dc70ec25/cmake/build_qt_with_openssl.cmake#L24) and add code like the one posted below to notify the developer early if the wrong Visual Studio command line prompt has been...

COMP: Streamline client project integration by explicitly including "vector"

4

This commit fixes regression introduced in b99fa7324 (Add several functions to the render window) allowing client project to successfully build without having to include "vector" header.

Fix use of renderWindow returned by CreateLookingGlassRenderWindow on macOS

9

Due to an issue in upstream VTK preventing windows with negative position from being used, the looking glass renderwindow created on macOS does not appear on the hardware display but...