View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004671 | Slicer4 | Core: Base Code | public | 2019-01-16 16:32 | 2019-05-17 10:58 |
Reporter | jcfr | Assigned To | sjh267 | ||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | closed | Resolution | fixed | ||
Product Version | |||||
Target Version | Slicer 4.10.2 | Fixed in Version | Slicer 4.10.2 | ||
Summary | 0004671: Backport | ||||
Description |
qSlicerWebWidget:
ExtensionBuildSystem:
| ||||
Tags | No tags attached. | ||||
It would be great if we could backport these bugfixes, too: Revision: a3cb76715f1158d5e0c1b17982ee7e1836e3fcc5
git-svn-id: http://svn.slicer.org/Slicer4/trunk@27946 3bd1e089-480b-0410-8dfb-8563597acbeeModified: Libs/MRML/DisplayableManager/vtkMRMLModelSliceDisplayableManager.cxx Revision: 62c7fe246ca3a149d36bf15b4d9d01c9aa27c214 This commit fixes a regression introduced in r27297 (ENH: added 3d views git-svn-id: http://svn.slicer.org/Slicer4/trunk@27948 3bd1e089-480b-0410-8dfb-8563597acbeeModified: Libs/MRML/Core/vtkMRMLCameraNode.cxx Revision: 3195e6d0bcd3ef29e383294a9b4e7ba13dfa9469 When hardening segmentation on a segmentation node containing planar contour master and closed surface, the conversion was performed multiple times, so it seemed like the application hang. Disabling an event for the hardening operation fixes this issue. A meaningless error message about the inability to get reference image geometry when there is no labelmap representation has been removed as well. Fixes https://github.com/SlicerRt/SlicerRT/issues/102 git-svn-id: http://svn.slicer.org/Slicer4/trunk@27953 3bd1e089-480b-0410-8dfb-8563597acbeeModified: Libs/MRML/Core/vtkMRMLSegmentationNode.cxx Revision: 0b13a3256492547d029be8e2a5f4afb42d30a693 In some cases Undo could not restore deleted segments. git-svn-id: http://svn.slicer.org/Slicer4/trunk@27954 3bd1e089-480b-0410-8dfb-8563597acbeeModified: Libs/vtkSegmentationCore/vtkSegmentationHistory.cxx Revision: 2c39ac184feb665d0a1f229b9fa089656a45612a Re https://discourse.slicer.org/t/export-dicom-rt-structure-as-segmentation/5797 git-svn-id: http://svn.slicer.org/Slicer4/trunk@27967 3bd1e089-480b-0410-8dfb-8563597acbeeModified: Modules/Loadable/Segmentations/Logic/vtkSlicerSegmentationsModuleLogic.cxx Revision: 4f2e0807f311d7ba0ab8c494f81c0b9203490d5d Since recent updates in VTK Qt widget, when a Segment Editor effect was active the mouse cursor remained the default arrow cursor. git-svn-id: http://svn.slicer.org/Slicer4/trunk@27971 3bd1e089-480b-0410-8dfb-8563597acbeeModified: Base/QTGUI/qSlicerMouseModeToolBar.cxx Revision: 0d7b9aee55293790d6c49fdbaa84991c7154d1a4 Co-authored-by: Davide Punzo <punzodavide@hotmail.it> git-svn-id: http://svn.slicer.org/Slicer4/trunk@28014 3bd1e089-480b-0410-8dfb-8563597acbeeModified: Base/Python/slicer/ScriptedLoadableModule.py Revision: 0a8e2d772f77d2a664b40fffd476e25f314e8f85 This was due to a Mac-specific Qt bug (https://bugreports.qt.io/browse/QTBUG-43344). Fixed using a simple flag preventing the second event to be handled. Co-authored-by: Csaba Pinter <csaba.pinter@queensu.ca> git-svn-id: http://svn.slicer.org/Slicer4/trunk@28012 3bd1e089-480b-0410-8dfb-8563597acbeeModified: Base/QTApp/qSlicerMainWindow.cxx Revision: c966c4890dadcfe1e4da418b0edda9b4e23236eb git-svn-id: http://svn.slicer.org/Slicer4/trunk@28011 3bd1e089-480b-0410-8dfb-8563597acbeeModified: Libs/MRML/Widgets/qMRMLSliceView.cxx Revision: 724ed0fb8ff9b9fce1dad4c73ed0ece495a63870
This is a good workaround for these unnecessary VTK messages. A discussion was From: Kyle Sunderland <sunderlandkyl@gmail.com> git-svn-id: http://svn.slicer.org/Slicer4/trunk@28018 3bd1e089-480b-0410-8dfb-8563597acbeeModified: Libs/MRML/DisplayableManager/vtkMRMLModelSliceDisplayableManager.cxx Revision: d6280e5741d3fb4ba2f025a4483e07523ef8a553 In some cases, for example, after changing font scale on Windows10, images only filled the bottom-left corner of slice view. Debugging revealed that devicePixelRatioF() returned 1.9999... while devicePixelRatio() returned 1. Using devicePixelRatioF to scale the view size fixed the issue. git-svn-id: http://svn.slicer.org/Slicer4/trunk@28025 3bd1e089-480b-0410-8dfb-8563597acbeeModified: Libs/MRML/Widgets/qMRMLSliceWidget.cxx Revision: d81595347e274ab7d2cd97665573b4c8311a6908 In some cases (when first segment was not the first segment alphabetically), Show 3D button had to be clicked twice to actually hide the segmentation. The problem was that segmentation removed closed surface representation one by one starting from the first segment in the segment map (alphabetically), and after each removal, a display update was triggered. The displayable manager checked representation of the first segment in the segment list (not necessarily ordered alphabetically), and recreated all missing representations. Displayable manager's assumption that all segments have the same representation was not valid because segment modified events were invoked while some of not all segments had the same representations. Fixed the issue by not invoking segment modified events until all the segments have the same representations. git-svn-id: http://svn.slicer.org/Slicer4/trunk@28059 3bd1e089-480b-0410-8dfb-8563597acbeeModified: Libs/vtkSegmentationCore/vtkSegment.cxx Revision: 08a67d8a16467353892a967be553d1dff3da1efd Problem was that there were multiple volume rendering display nodes in the scene and the first one was invalid (there was not volume associated with it). Even though the user enabled visibility, the volume was not rendered because of the missing volume node association. Fixed by ignoring corrupted display nodes. User who created the offending scene reported that only Slicer GUI was used, therefore the root cause of the problem (having two volume rendering display nodes, one of them is invalid) is not addressed by this commit. git-svn-id: http://svn.slicer.org/Slicer4/trunk@28060 3bd1e089-480b-0410-8dfb-8563597acbeeModified: Modules/Loadable/Segmentations/Widgets/qMRMLSegmentEditorWidget.cxx Revision: 89de5b3770fa6908ee71495f96f2080662438ee1 git-svn-id: http://svn.slicer.org/Slicer4/trunk@28063 3bd1e089-480b-0410-8dfb-8563597acbeeModified: Modules/Loadable/Segmentations/Logic/vtkSlicerSegmentationsModuleLogic.cxx Revision: 32d2f96fa19876de319fa9b75aac56754a90ab5d git-svn-id: http://svn.slicer.org/Slicer4/trunk@28065 3bd1e089-480b-0410-8dfb-8563597acbeeModified: Modules/Scripted/LabelStatistics/LabelStatistics.py Revision: 7ea34865ccc330bda78a6b75bb0fe407445934f5 This commit fixes -Wempty-body warning git-svn-id: http://svn.slicer.org/Slicer4/trunk@28097 3bd1e089-480b-0410-8dfb-8563597acbeeModified: Libs/MRML/DisplayableManager/vtkMRMLScalarBarDisplayableManager.cxx Revision: 910376055ac44f69bbdca3f96993691a957036ff Segmentation could not be loaded directly from a generic nrrd file (that did not have any segmentation specific fields) because segment name was not filled and uninitialized segment name caused a crash. Fixed by using segment ID as segment name if segment name is not specified. git-svn-id: http://svn.slicer.org/Slicer4/trunk@28139 3bd1e089-480b-0410-8dfb-8563597acbeeModified: Libs/MRML/Core/vtkMRMLSegmentationStorageNode.cxx Revision: 2fe008bc58f762772bf92f5ec019ff5aa512db05 sliceWidget() method expects slice node name and not layout name. git-svn-id: http://svn.slicer.org/Slicer4/trunk@28216 3bd1e089-480b-0410-8dfb-8563597acbeeModified: Modules/Scripted/DataProbe/DataProbe.py Revision: 05b9129eb779cc163110725485d7bfab3ac3f0f6 Prevent throwing an error when examining slice positions in a multi-frame DICOM file (just log a warning). git-svn-id: http://svn.slicer.org/Slicer4/trunk@28225 3bd1e089-480b-0410-8dfb-8563597acbeeModified: Modules/Scripted/DICOMPlugins/DICOMScalarVolumePlugin.py |
|
Backporting into 4.10.2 completed |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2019-01-16 16:32 | jcfr | New Issue | |
2019-01-16 16:32 | jcfr | Status | new => assigned |
2019-01-16 16:32 | jcfr | Assigned To | => sjh267 |
2019-01-16 16:33 | jcfr | Description Updated | View Revisions |
2019-01-18 00:38 | jcfr | Description Updated | View Revisions |
2019-04-26 13:43 | jcfr | Description Updated | View Revisions |
2019-04-26 13:43 | jcfr | Description Updated | View Revisions |
2019-04-26 15:08 | jcfr | Description Updated | View Revisions |
2019-05-14 10:04 | lassoan | Note Added: 0016259 | |
2019-05-17 10:58 | sjh267 | Status | assigned => closed |
2019-05-17 10:58 | sjh267 | Resolution | open => fixed |
2019-05-17 10:58 | sjh267 | Fixed in Version | => Slicer 4.10.2 |
2019-05-17 10:58 | sjh267 | Note Added: 0016261 |