View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0002473Slicer4Module Annotationspublic2012-09-04 12:342013-09-03 16:28
Reporterlassoan Assigned Tonicole  
PrioritynormalSeveritymajorReproducibilityalways
Status closedResolutionfixed 
Product Version 
Target VersionSlicer 4.2.0Fixed in VersionSlicer 4.2.0 
Summary0002473: Fiducials appear on incorrect slice if visibility is enabled in data module
Description

If the user clicks on the eye icon of a fiducial in the data module then the fiducial point appear on all slice viewers, regardless of which slice is selected in the viewers.

How to reproduce:

  • Load the MRI head sample
  • Add 3 fiducials on a slice
  • Change slice => fiducials are not visible anymore
  • Go to Data module
  • Choose "Displayable hierarchy" view
  • Click on the eye icon of any fiducial
    => ERROR: the fiducial appear in all slice viewers (although it was marked on a different slice)

Tested on Slicer-4.1.0-2012-09-03-win-amd64.exe.

TagsNo tags attached.

Activities

lassoan

lassoan

2012-10-06 05:26

developer   ~0006416

The same problem happens (the fiducial appear in a completely wrong slice) if the fiducial is edited in the annotation module (e.g., fiducial or text size or color is changed). Showing a fiducial point in a completely wrong position (wrong slice) is a quite serious problem.
nicole

nicole

2012-10-11 10:50

administrator   ~0006499

svn 21159 fixes the eye icon state when looking at the fiducials in the displayable view in the data module.
nicole

nicole

2012-10-23 16:19

administrator   ~0006713

On linux, a quick test shows this only happening with fiducials, rulers and rois don't show up on all three slices.
nicole

nicole

2012-10-26 11:29

administrator   ~0006818

Fixed the logic that determined if the widget was visible on this slice.
svn 21258

http://viewvc.slicer.org/viewvc.cgi/Slicer4/trunk/Modules/Loadable/Annotations/MRMLDisplayableManager/vtkMRMLAnnotationDisplayableManagerHelper.cxx?r1=21258&r2=21257&pathrev=21258
lassoan

lassoan

2013-09-03 16:28

developer   ~0009880

The problem is not reproducible anymore (tested on Slicer-4.2.2-2013-08-28).

Issue History

Date Modified Username Field Change
2012-09-04 12:34 lassoan New Issue
2012-09-04 12:34 lassoan Status new => assigned
2012-09-04 12:34 lassoan Assigned To => nicole
2012-10-06 05:26 lassoan Note Added: 0006416
2012-10-09 06:19 nicole Target Version => Slicer 4.2.0 - coming release
2012-10-11 10:50 nicole Note Added: 0006499
2012-10-23 16:19 nicole Note Added: 0006713
2012-10-26 11:29 nicole Note Added: 0006818
2012-10-26 11:29 nicole Status assigned => resolved
2012-10-26 11:29 nicole Fixed in Version => Slicer 4.2.0 - coming release
2012-10-26 11:29 nicole Resolution open => fixed
2013-09-03 16:28 lassoan Note Added: 0009880
2013-09-03 16:28 lassoan Status resolved => closed