View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0001690 | Slicer4 | Module Markups | public | 2012-02-07 09:26 | 2018-05-30 00:35 |
Reporter | pieper | Assigned To | nicole | ||
Priority | normal | Severity | major | Reproducibility | always |
Status | assigned | Resolution | open | ||
Product Version | |||||
Target Version | backlog | Fixed in Version | |||
Summary | 0001690: fiducial shows in wrong lightbox cell | ||||
Description | When the annotation belongs in the upper left cell of a lightbox, it actually shows up in the lower left cell. See attached image. | ||||
Steps To Reproduce | Load MRHead data Switch to any lightbox mode, say 6x6 and see that the annotation should be in the upper left cell but is in the lower left instead. | ||||
Tags | No tags attached. | ||||
related to | 0002732 | closed | millerjv | Move LightBox proxy to abstract displayable manager for easier re-use |
parent of | 0002821 | closed | pieper | fiducials move on mouse over |
related to | 0001914 | closed | jcfr | fiducial points misplaced after switching layouts |
related to | 0002823 | acknowledged | nicole | Rulers not working in lightbox mode |
related to | 0003690 | assigned | nicole | Markups: Implement hack/workaround for 0001690 and 0003531 |
related to | 0003761 | closed | nicole | Markups: test_MarkupsInCompareViewersSelfTest1 is failing |
2012-02-07 09:26
|
|
From group discussion> Better not to show it than to show it in the wrong place... |
|
Fiducial and ruler do this (show up in the bottom left hand slice in the lightbox), but the ROI seems to behave properly. |
|
ENH: Easier re-use by adding static sliceView DisplayableManager "Convert" methods See r21245 / http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=21245 |
|
JC: This seems to be a step in the right direction, I have to do the opposite (RAS -> Device) when placing the widgets to make sure it's fully working, doing that now.... |
|
Nicole: It means you should probably be adding the static method :ConvertXYZToDevice to vtkMRMLAbstractSliceViewDisplayableManager Then, you will be able to do: vtkMRMLAbstractSliceViewDisplayableManager::ConvertRAStoXYZ(...) Adding the static convenience method: ConvertRAStoDevice to vtkMRMLAbstractSliceViewDisplayableManager could also be helpful. |
|
I'm working in display coordinates rather than device/viewport coordinates with the annotation widgets (as much as possible anyway), since the display coordinates give me the index into lightbox slices as well. |
|
device is display coordinate. Isn't it ? This at least what I understood reading the comment in Jim code. I then reported it in the doxygen. |
|
device is viewport coordinates, from what I understood from the code. |
|
Based on q quick experiment where I added the following code: std::cout << "Device(x:" << pos[0] << ", y:" << pos[1] << ") - XYZ(x:" << xyz[0] << ", y:" << xyz[1] << ", z:" << xyz[2] << ")" << std::endl; at line 755 of vtkMRMLCrosshairDisplayableManager.cxx [1] Setting the red slice to a 3*2 lightbox, we can clearly see that: Device is display coordinate: Where in the RenderWindow the mouse pointer is XYZ is view port coordindate: Coordindate within a given viewport Associated log: Entered in (1) (see enclosed screenshot) |
|
2012-10-25 15:01
|
|
According to my understanding of VTK rendering terminology, viewport coordinates always fall between 0-1, they're a normalised version of display coordinates achieved by dividing by the window width/height. Working on updating vtkMRMLAnnotationDisplayableManager::GetWorldToDisplayCoordinates |
|
Disabling showing fiducials and rulers in 2d slice viewers that are in lightbox mode (also compare viewers as they use lightbox). svn 21263. http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=21263 Revisit after RSNA |
|
Cleaned up the displayable manager code a bit in svn 21310[1], updated conversion of RAS to display coordinates to use vtkMRMLAbstractSliceViewDisplayableManager::ConvertRASToXYZ( [1] http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=21310 |
|
Noticed that the number of renderers doesn't necessarily match the number of light boxes (seems to grow but not shrink), so check the lightbox index first in svn 21312[1] and also check if the widget needs it's renderer reset to avoid flickering. The current code also disables moving the widgets while in lightbox mode, that will need to be addressed. Looking at the Crosshair displayable manager, I think that the annotation displayable managers may need to include a vtkLightBoxRendererManager (from CTK) in order to be able to get the correct renderer to assign to the widgets. [1] http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=21312 |
|
After some research and debugging, Nicole and I realized that the (one) underlying issue is that the render window has more renderers than lightbox cells. This was something Jim apparently ran into and fixed about a year ago for the crosshairs, and he added a proxy that gives access to ctk's lightbox manager. This is needed in order to map XYZ coordinates to the proper renderer, but this has not been generalized to support other displayable managers. (Note that the vtkMRMLModelSliceDisplayableManager also only displays in the first cell of a lightbox. Suggestions: For 4.2.1: move the lightbox proxy up to the abstract displayable manager class level so that it is available to all displayable manager subclasses. This would mean adding it to the initialize methods for the displayable manager groups. ThreeD displayable managers could just return the single renderer, while slice views could use the proxy to get the correct renderer for the given coordinate (Z coordinate of XYZ space). For 4.3: factor out more of the redundant code from displayable managers into the abstract class. Functionality to factor out:
|
|
Another question to investigate: why are there extra renderers in the slice view render windows that do not get removed. Specifically, at startup there are 2 renderers, then going to 3x3 lightbox mode there become 10 renderers (going back to 1x1 there are still 10 renderers). Going to 6x6 led to 45 renderers, and those remain even after going back to 1x1 mode. |
|
Reminder sent to: jcfr, millerjv Jim and Jc - could you review the latest notes on this and comment as needed? -Steve and Nicole |
|
I had forgotten about the lightboxmanagerproxy. Yes, I had that same issue that I couldn't map to the correct renderer without asking CTK do it. Of course, the display able managers don't know about CTK, hence the proxy. I always thought there one extra renderer for the overlay plane. That assumption sounds good until your 6x6 example. |
|
Yes, we were also confused by why there are ever extra and/or non-consistent renderers. We did another test where we tried to only use the last row x column renders in the list but that didn't appear to work either. |
|
Note 7029 sounds like a good approach, I would be happy to review topic regarding the moving of the proxy. I create issue 0002732 to track it and it is assigned to Jim. Jim> Can you take care of the refactor ? NOTE: When done, the change should NOT be pushed on the trunk. Instead, a github topic should be referenced as a note to issue 0002732 for review. |
|
JC, since you do not want this immediately pushed to the trunk, do you want to this based off a particular branch? trunk or 4.2? |
|
Jim: Just based your topic on today's master. git chechout -b 2732-move-lightbox-to-abstract-displayable-manager Nicole will then based her topic named "1690-fiducial-shows-in-wrong-lightbox-cell" on yours. |
|
Jim: any updates? |
|
Pushed a patch to https://github.com/millerjv/Slicer4/commit/55f9c1c637f4ef4ba5c0da8b442aac57626d10c7 Branch is "2732-move-lightbox-to-abstract-displayable-manager" commit 55f9c1c637f4ef4ba5c0da8b442aac57626d10c7 |
|
Thanks Jim. Looks great. Nicole> Is this sufficient for you to make progress ? |
|
branched from jim's branch and got my github Slicer fork update, but my first attempt to use the GetRenderer(idx) didn't work, will continue in the morning. |
|
Hi Nicole, Any update regarding that issue ? Are the change of Jim working for you ? Can his topic be integrated ? Thanks |
|
Jim's change is helpful, but the problem turned out to be that the widgets being used in the 2d views were using 3d handle representations, and their cameras weren't correct. I cleaned up the first part of the fix and pushed to my github: |
|
Have the 2d point handle mostly working : The main problem left is that when you switch into and out of light box mode, the fiducials aren't getting their handles updated. They will update once the fid is moved in 3d, but that's not ideal. |
|
Thanks for the update. Seems important progress are made :) |
|
Okay, done for now: https://github.com/naucoin/Slicer/commits/1690-fiducial-shows-in-wrong-lightbox-cell I'm going to submit an experimental build to the dashboard (host name b2-d4-10.bwh.harvard.edu) to see what happens, will look at it again in the morning. |
|
I did some more testing with the prostate demo scene. It looks like things are very close - the crash I found is an issue in VTK - the WorldToView method checks for ActiveCamera, but the ViewToWorld doesn't -- the patch below fixes this and makes the prostate scene load correctly. There is still the issue that you need to trigger some of the updates manually in order for fiducials to appear. We should look at the scene with Andrey to be sure the fiducials are in the right places. 0000159 Slicer-superbuild $ (cd VTK; git diff) // get the perspective transformation from the active camera
|
|
Steve: Thanks for proposing the VTK patch. I guess now is the good time to get your gerrit account for VTK :) See http://www.vtk.org/Wiki/VTK/Git/Develop |
|
Nicole> Jim changes regarding lightbox proxy have been integrated. I am assuming the following commits of your topic are final ? Talking about these commits: https://github.com/naucoin/Slicer/compare/555faa90001b8af89a31a98202142539cb35476e...1690-fiducial-shows-in-wrong-lightbox-cell |
|
Those commits are final, but I'm working on another one to try and fix the prostate demo crash (hopefully just need to set the renderer on the widget representation in create widget). |
|
Nope, quick fix didn't work. |
|
This is kind of odd: in the debugger, at the crash point the renderer is valid but the camera is not: as I was poking through the backtrace, I called GetActiveCamera() and it kept returning a valid camera. Back to frame 0, and the camera is all of a sudden valid again. It turns out that GetActiveCamera sets a camera if one isn't defined according to vtkRenderer.h. |
|
Pushed a patch to my github[1], making sure to check for a valid renderer and active camera before trying to set the display position on the seeds. Also make sure that on creation that the seed and represetnation have the correct and same renderers. [1] https://github.com/naucoin/Slicer/commit/813046dc70286c7f81a7c5d4b125e9a5f3f2653d |
|
Does it still make sens to rush with last minute code that may break stuff ? |
|
Found another issue: the light box in which to display a fiducial isn't being correctly determined if the volume slice spacing is != 1. In light of this, since we're back to the annotations occasionally showing up in the wrong place, Steve and I feel that we can retarget this for 4.2.2. |
|
I think the central issue here is that the widgets rely on the CAMERA to properly convert to/from world coordinates. However, Slicer really doesn't utilize the camera in the 2D views. The situation get muddled further when in lightbox mode. It is hard to follow the code but all the panes in the lightbox may share the same camera. I think what needs to happen is that each renderer in the lightbox needs to have a unique camera AND each camera needs to configured specific for the slice that camera is displaying. This is so the widget/coordinate classes can utilize the camera projection matrix to go from World to View to Normalized Viewport to Viewport to Normalized Display to Display. The problem here is that all the current renderering in the SliceViews assumes a default camera since handle all the mapping ourselves. |
|
Base on recent finding and discussion. Retargeted for 4.2.2 (Dec 1st) Make sure to update your topic so that it is based on current trunk: Rename topicgit checkout 1690-fiducial-shows-in-wrong-lightbox-cell Update mastergit checkout master Create new topic and cherry pick commit of interestgit checkout -b 1690-fiducial-shows-in-wrong-lightbox-cell Delete local obsolete topicgit branch -D 1690-fiducial-shows-in-wrong-lightbox-cell-old Push new version of the topic on your forkgit push naucoin 1690-fiducial-shows-in-wrong-lightbox-cell --force |
|
Thanks for the steps. I'm not using git svn, so I had to use |
|
From hangout discussion> Make sure to consider spacing when going from Ras to lightbox coordinate. |
|
Checked in an update to my github that takes into account volume slice spacing when in light box mode - only show fiducials that are within 0.5mm of a light box slice. Still working on debugging the swapping between 2d and 3d handles when switch between light box and 1x1 mode. |
|
1) Extra. I added few comment on the last commit of the topic 2) Is the issue "swapping between 2d and 3d handles" a show stopper or simply a aesthetic details ? 3) Steve mentioned he would be working on the "snapping" of annotation to closed slice, has this been addressed yet ? |
|
Hi Jc - Regarding your third point, see child issue 0002821. Nicole will respond on the others. |
|
It looks like the current state of my github branch fixes the issues (except for a random reset to a starburst glyph instead of the circle glyph when coming back to 1x1 mode) on Mac, though Linux is still having update/renderer issues (fids show in the wrong light box cell, but update correctly on scroll). |
|
github commit de6aa0c fixed the glyph update when switching out of light box mode. |
|
as of svn 21495, work from github ported back to Slicer trunk. Rulers are disabled, but fiducials are re-enabled. |
|
Should the issue be resolved ? An other issue to keep track of the fact Ruler are disabled could be created. |
|
There are still some issues with the display on Linux that I'd like to try and track down, but I created another issue for the rulers since they'll have their own special cases, bug # 2823 |
|
Would it be possible to list the know issues, I will then mention them in the release notes. We should probably create separate issue to track this specific issues. That we will be able to close this one. Would that make sens ? |
|
When switching into lightbox mode on some Linux systems (SPL workstations show this behaviour), the fiducials sometimes don't update their position until the slices are scrolled. |
|
2012-12-07 13:33
|
|
2012-12-07 13:33
|
|
Download sample data: MRHead Step1: Lay down some fiducials along the slicer intersection See screenshots issue1690_r21495_step{1,2}.png |
|
I can't replicate the crash reported in 7461. Can you generate a stack trace? |
|
Experience 2: 1) Load sample data MRHead [[ 2) Enable slice interaction ]] -> don't think that is related to the issue 3) Set annationation mode to persistent 4) Lay down a lot of fiducial. 5) Switch yellow slice to 1x6 light box. 6) Try to select the cross -> impossible to really move them. 7) Go back to normal view 1x1 8) Go back to 1x6 - move fiducial and or the cross -> crash |
|
2012-12-07 13:44
|
|
2012-12-07 13:44
|
|
2012-12-07 13:44
|
|
2012-12-07 13:46
|
|
2012-12-07 17:14
|
|
2012-12-07 17:14
|
|
Experience 3: Associated screenshots shows the corresponding stacktrace |
|
I was never able to get it to crash, but I did see that in 1xN modes the conversion from 3D to 2D fiducials and back again wasn't reliable. I can see how this would lead to a crash. I didn't see this for MxN modes where M > 1 so that may be a clue for debugging. |
|
Following JC's steps in note 7463 I was able to get a crash as well. Only some of the fiducials that I placed updated to 2d/3d when swapping in and out of lightbox, but as I interacted with them via the Fids module GUI, updates led to the 3d ones disappearing entirely. Part of it is that the visibility check is done first (is the fid in the fov of the new narrower viewport brought about by swapping to 1xN mode?) and then the 2d/3d update is triggered and that does't happen if the fid isn't visible. Still tracing through all the paths that various events can lead to to try and shut down the error cases. |
|
Reminder sent to: millerjv From Nicole: Could you comment on this issue ? |
|
Double checked this with the Markups module, no crashing, but it is showing some odd behaviour that I think is related to the slice node / layout update and widget refresh rate. |
|
Reminder sent to: millerjv Jim: Could you try running the MarkupsInCompareViewers test from the SelfTest GUI? Look at the error messages and you can see that there are complaints about not having a valid slice node in the displayable manager (see below) as it switches between compare view layouts. I think this is one of the causes of odd behaviour with the fiducials as the user switches between numbers of lightboxes/compare views, the layout update and the displayable manager update get a bit out of synch. ERROR: In /projects/birn/nicole/Slicer42/Slicer/Modules/Loadable/Markups/MRMLDM/vtkMRMLMarkupsDisplayableManager2D.cxx, line 1168 ERROR: In /projects/birn/nicole/Slicer42/Slicer/Modules/Loadable/Markups/MRMLDM/vtkMRMLMarkupsDisplayableManager2D.cxx, line 783 ERROR: In /projects/birn/nicole/Slicer42/Slicer/Modules/Loadable/Markups/MRMLDM/vtkMRMLMarkupsDisplayableManager2D.cxx, line 1168 ERROR: In /projects/birn/nicole/Slicer42/Slicer/Modules/Loadable/Markups/MRMLDM/vtkMRMLMarkupsDisplayableManager2D.cxx, line 783 ERROR: In /projects/birn/nicole/Slicer42/Slicer/Modules/Loadable/Markups/MRMLDM/vtkMRMLMarkupsDisplayableManager2D.cxx, line 1168 ERROR: In /projects/birn/nicole/Slicer42/Slicer/Modules/Loadable/Markups/MRMLDM/vtkMRMLMarkupsDisplayableManager2D.cxx, line 783 |
|
Still working on this one, don't think it'll be done by Tuesday morning.
Program received signal SIGSEGV, Segmentation fault. The crux of the current problem with changing |
|
Possibly related issue found while trying to debug missing key press events: I think I copied the method to add an initial initialize step in the displayable mangers from a source with a typo in it. Doing a quick test to see what happens when I take the extra n out of the camera displayable manager, I noticed that it's got an assert, and that it's setting the active camera on the renderer, which might explain some of the problems seen in this bug if it wasn't getting triggered. Building now and will run tests and upload them to the dashboard with the camera displayable manager change. |
|
Spelling mistakes are nasty bugs. Had one a while ago where the function name in the superclass had a typo. So my classes correctly spelled function override was never called. Did this fix the issue? |
|
Unfortunately it didn't fix this issue, but I suspect that's partially because I'd already put in code to catch null pointers. I want to check in the fix though as it is a bug and it didn't break any of the tests when I submitted an experimental build, these failing tests are due to a corrupted mrb and a widget size check failing: Checked in the fix as svn 22611: |
|
Backported r22611 to branch Slicer-4-3. See http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=22626 |
|
Will take another run at resolving this issue, but if not we will disable the fiducials when in light box mode and provide a dialog box warning users that fiducials will disappear when going into light box mode. |
|
@Steve, @nicole: What about re-using the logic used by the cross-hair ? |
|
@jcfr I'm fine with that. @Nicole let us know if you need another set of eyes on this. |
|
I already implemented the cross hair logic, the error is currently from using the vtkSeedWidget as a 2d implementation. I have some code in a topic branch that might fix it, I need to rebase it and recheck it. |
|
Excellent. Let me know if you like me to test a topic. |
|
For reference, commit r23841 [1] should help to address the "no active camera" warning/issue. [1] http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=23841 |
|
Disabling fiducials in light box mode: I¹m fairly certain that this logic check is backward since the point handles were becoming visible again when I¹d mouse near them after turning their visibility off: |
|
Considering the documentation: // Description: the code makes sense. By setting the property "ActiveRepresentation" to 1, the widget will be hidden if the mouse is away, and visible if it is nearby. That said, to ensure that the visibility of a widget representation is not affected by the mouse, seems you need to disable the widget to ensure mouse interaction won't affect the visibility of the associated representations. For markups, that means that:
In any case, ActiveRepresentation should be set to 0. |
|
Thanks for the clarification, I'll double check my logic! I'm still unable to get the seed widget to behave properly when swtiching between lightbox and non light box modes in terms of having the correct types of handles (I'd tried to fix this issue by moving to 2d point handles when in light box) and the correct number of handles (found a state where there's a mix of types). Will pick it up again tomorrow, I won't be able to fix it tonight. |
|
For the ActiveRepresentatin, this is the annotated code snippet that's confusing me: I see what you mean about the enabled state, but it seems backward to me that this is the current default behaviour (with active representation off): |
|
Topic branch disabling showing fiducials has been pushed: |
|
Integrated in r24726 Note that in rr24727, I added a check to disable the popup if testing is enabled. |
|
Considering how difficult (I would say practically nearly impossible) to implement interactions correctly in lightbox views - what about taking a different approach and generating lightbox views as static image mosaics instead? Posted more details and asked for feedback here: https://discourse.slicer.org/t/who-uses-lightbox-view/495 |
|
Retarget stale issues to backlog. |
|
Slicer: 2145-support-for-installing-extension-from-file 15908f5b 2012-12-07 14:53:01 naucoin Details Diff |
BUG: fix fiducial display in light box mode. Use the renderer from the light box proxy manager if it's defined When in light box mode, switch to using 2d point handles for fiducials. Avoid seed widget and representation having different renderers on creation. Unify light box index calculation. Fix the annotations showing up in the 0th light box when the annotation should be in the -1th. Take into account volume spacing, calculate the distance between the fiducial and the slice at this light box index using distance from the fiducial point and the slice plane. Reset the glyph type when changing in and out of lightbox mode. Issue 0001690 git-svn-id: http://svn.slicer.org/Slicer4/trunk@21494 3bd1e089-480b-0410-8dfb-8563597acbee |
||
mod - Applications/SlicerApp/Testing/Python/CMakeLists.txt | Diff File | ||
mod - Base/QTCore/qSlicerSceneBundleIO.cxx | Diff File | ||
mod - Modules/Loadable/Annotations/MRMLDisplayableManager/vtkMRMLAnnotationDisplayableManager.cxx | Diff File | ||
mod - Modules/Loadable/Annotations/MRMLDisplayableManager/vtkMRMLAnnotationDisplayableManager.h | Diff File | ||
mod - Modules/Loadable/Annotations/MRMLDisplayableManager/vtkMRMLAnnotationFiducialDisplayableManager.cxx | Diff File | ||
Slicer: 2145-support-for-installing-extension-from-file d02e772f 2013-10-14 11:58:40 naucoin Details Diff |
BUG: fix typo in AdditionalInitializeStep method name Fixing a mis spelling in the additional initialize step method name. In vtkMRMLAbstractDisplayableManager it's defined as: AdditionalInitializeStep but vtkMRMLCameraDisplayableManager was using: AdditionnalInitializeStep with an extra n. Using that signature, it was never getting called so when new layout windows were being created, the active camera was not getting set on the renderer. Issue 0001690 git-svn-id: http://svn.slicer.org/Slicer4/trunk@22611 3bd1e089-480b-0410-8dfb-8563597acbee |
||
mod - Libs/MRML/DisplayableManager/vtkMRMLCameraDisplayableManager.cxx | Diff File | ||
mod - Libs/MRML/DisplayableManager/vtkMRMLCameraDisplayableManager.h | Diff File | ||
Import 2017-06-07 23:51:09: master 5bda82b9 2014-12-20 22:15:09 Details Diff |
BUG: Update CTK to fix Fix warning related to missing active camera // ---------- vtkLightBoxRendererManager - Fix warning related to missing active camera This issue was occurring after (1) adding a markup and (2) registering a custom Slicer layout having at least on Slice view. It addresses the following warning: WorldToView: no active camera, cannot compute world to view, returning 0,0,0 The "no active camera" warning/issue is also discussed in Slicer issue 0001690 but note that this commit does NOT address that problem. // ---------- $ git shortlog cb53ac3..07222d0 --no-merges Jean-Christophe Fillion-Robin (1): vtkLightBoxRendererManager - Fix warning related to missing active camera git-svn-id: http://svn.slicer.org/Slicer4/trunk@23841 3bd1e089-480b-0410-8dfb-8563597acbee |
||
mod - SuperBuild/External_CTK.cmake | Diff File | ||
Import 2017-06-07 23:51:09: master 0a7c91eb 2015-11-11 17:31:58 Details Diff |
BUG: Disable fiducials in light box mode. See 0001690 Fiducials are not being properly positioned when in light box mode, this change disables them and gives the user a warning that they are being disabled (new fiducials can still be placed, but will not be visible until you exit light box mode). This change fixes bugs that were left from the attempt to use the point handle widgets in 2D so that they can be properly hidden: fix the visibility setting on the point handles in light box mode, disable the point handles when invisible so that they don't become visible when the mouse is near it, updated a visibility check comparision to match return type from method. Also removed warning messages by casting the 3d handles before changing the picking state. Fixed a bug wherein if you had a mix of fiducials having been placed in lightbox and not light box mode, the seed widget would have a mix of 2d and 3d handles. This fix removes all the current handles so that they're properly recreated as the necessary type. Issue 0001690 From: Nicole Aucoin <nicole@bwh.harvard.edu> git-svn-id: http://svn.slicer.org/Slicer4/trunk@24726 3bd1e089-480b-0410-8dfb-8563597acbee |
||
mod - Libs/MRML/Widgets/qMRMLSliceControllerWidget.cxx | Diff File | ||
mod - Modules/Loadable/Markups/MRMLDM/vtkMRMLMarkupsDisplayableManager2D.cxx | Diff File | ||
mod - Modules/Loadable/Markups/MRMLDM/vtkMRMLMarkupsFiducialDisplayableManager2D.cxx | Diff File |
Date Modified | Username | Field | Change |
---|---|---|---|
2012-02-07 09:26 | pieper | New Issue | |
2012-02-07 09:26 | pieper | Status | new => assigned |
2012-02-07 09:26 | pieper | Assigned To | => nicole |
2012-02-07 09:26 | pieper | File Added: Selection_181.png | |
2012-08-20 09:53 | nicole | Target Version | => Slicer 4.2.0 - Feature freeze Sept 1st 2012 |
2012-08-20 11:46 | jcfr | Note Added: 0005625 | |
2012-08-20 12:01 | jcfr | Relationship added | related to 0001914 |
2012-10-23 16:23 | nicole | Note Added: 0006715 | |
2012-10-25 12:08 | jcfr | Note Added: 0006758 | |
2012-10-25 12:40 | nicole | Note Added: 0006767 | |
2012-10-25 13:22 | jcfr | Note Added: 0006775 | |
2012-10-25 13:43 | nicole | Note Added: 0006780 | |
2012-10-25 13:59 | jcfr | Note Added: 0006783 | |
2012-10-25 14:33 | nicole | Note Added: 0006797 | |
2012-10-25 14:58 | jcfr | Note Added: 0006800 | |
2012-10-25 15:01 | jcfr | File Added: Screenshot-issue-1690-note-6800.png | |
2012-10-26 08:00 | nicole | Note Added: 0006809 | |
2012-10-26 17:57 | nicole | Note Added: 0006827 | |
2012-10-26 17:57 | nicole | Status | assigned => acknowledged |
2012-10-26 17:58 | nicole | Target Version | Slicer 4.2.0 - coming release => Slicer 4.3.0 |
2012-11-02 10:45 | nicole | Note Added: 0007023 | |
2012-11-02 10:45 | nicole | Status | acknowledged => assigned |
2012-11-02 10:45 | nicole | Target Version | Slicer 4.3.0 => Slicer 4.2.1 |
2012-11-02 13:32 | nicole | Note Added: 0007026 | |
2012-11-02 15:14 | pieper | Note Added: 0007029 | |
2012-11-02 15:16 | pieper | Note Added: 0007030 | |
2012-11-02 15:18 | pieper | Note Added: 0007031 | |
2012-11-02 15:29 | millerjv | Note Added: 0007032 | |
2012-11-02 15:36 | pieper | Note Added: 0007033 | |
2012-11-05 10:37 | jcfr | Note Added: 0007052 | |
2012-11-06 09:50 | jcfr | Relationship added | related to 0002732 |
2012-11-06 10:22 | millerjv | Note Added: 0007084 | |
2012-11-06 12:28 | jcfr | Note Added: 0007088 | |
2012-11-12 06:23 | nicole | Note Added: 0007161 | |
2012-11-14 06:43 | millerjv | Note Added: 0007210 | |
2012-11-14 06:51 | jcfr | Note Added: 0007214 | |
2012-11-14 13:08 | nicole | Note Added: 0007224 | |
2012-11-15 13:22 | jcfr | Note Added: 0007255 | |
2012-11-15 14:37 | nicole | Note Added: 0007264 | |
2012-11-15 14:45 | nicole | Note Edited: 0007264 | |
2012-11-15 16:49 | nicole | Note Added: 0007265 | |
2012-11-15 17:00 | jcfr | Note Added: 0007269 | |
2012-11-15 17:16 | nicole | Note Added: 0007270 | |
2012-11-16 03:55 | pieper | Note Added: 0007274 | |
2012-11-16 05:26 | jcfr | Note Added: 0007278 | |
2012-11-16 06:42 | jcfr | Note Added: 0007284 | |
2012-11-16 06:46 | nicole | Note Added: 0007285 | |
2012-11-16 06:52 | nicole | Note Added: 0007286 | |
2012-11-16 07:23 | nicole | Note Added: 0007289 | |
2012-11-16 07:50 | nicole | Note Added: 0007290 | |
2012-11-16 08:57 | jcfr | Note Added: 0007291 | |
2012-11-16 09:40 | nicole | Note Added: 0007293 | |
2012-11-16 10:13 | millerjv | Note Added: 0007296 | |
2012-11-16 10:14 | millerjv | Note Edited: 0007296 | |
2012-11-16 10:21 | jcfr | Target Version | Slicer 4.2.1 => Slicer 4.2.2 |
2012-11-16 10:25 | jcfr | Note Added: 0007297 | |
2012-11-16 10:54 | nicole | Note Added: 0007299 | |
2012-12-04 11:30 | jcfr | Note Added: 0007410 | |
2012-12-06 11:26 | nicole | Note Added: 0007423 | |
2012-12-06 12:11 | pieper | Relationship added | parent of 0002821 |
2012-12-06 13:17 | jcfr | Note Added: 0007428 | |
2012-12-06 13:38 | pieper | Note Added: 0007429 | |
2012-12-06 13:51 | nicole | Note Added: 0007431 | |
2012-12-06 14:55 | nicole | Note Added: 0007442 | |
2012-12-07 10:00 | nicole | Note Added: 0007454 | |
2012-12-07 11:07 | jcfr | Note Added: 0007456 | |
2012-12-07 11:29 | nicole | Relationship added | related to 0002823 |
2012-12-07 11:30 | nicole | Note Added: 0007457 | |
2012-12-07 11:35 | jcfr | Note Added: 0007458 | |
2012-12-07 11:36 | jcfr | Note Edited: 0007458 | |
2012-12-07 11:38 | nicole | Note Added: 0007459 | |
2012-12-07 13:33 | jcfr | File Added: issue1690_r21495_step1.png | |
2012-12-07 13:33 | jcfr | File Added: issue1690_r21495_step2.png | |
2012-12-07 13:34 | jcfr | Note Added: 0007461 | |
2012-12-07 13:36 | jcfr | Note Edited: 0007461 | |
2012-12-07 13:40 | pieper | Note Added: 0007462 | |
2012-12-07 13:43 | jcfr | Note Added: 0007463 | |
2012-12-07 13:44 | jcfr | File Added: experience2_issue1690_r21495_step1.png | |
2012-12-07 13:44 | jcfr | File Added: experience2_issue1690_r21495_step2.png | |
2012-12-07 13:44 | jcfr | File Added: experience2_issue1690_r21495_step3.png | |
2012-12-07 13:46 | jcfr | File Added: experience2_issue1690_r21495_step5.png | |
2012-12-07 13:47 | jcfr | Note Edited: 0007463 | |
2012-12-07 13:48 | jcfr | Note Edited: 0007463 | |
2012-12-07 17:14 | jcfr | File Added: experience3_issue1690_r21495_slicer.png | |
2012-12-07 17:14 | jcfr | File Added: experience3_issue1690_r21495_stacktrace.png | |
2012-12-07 17:15 | jcfr | Note Added: 0007464 | |
2012-12-07 18:01 | jcfr | Target Version | Slicer 4.2.2 => Slicer 4.2.3 |
2012-12-08 04:29 | pieper | Note Added: 0007466 | |
2012-12-24 09:40 | nicole | Note Added: 0007575 | |
2013-02-12 09:37 | jcfr | Target Version | Slicer 4.2.3 => Slicer 4.3.0 |
2013-08-20 12:12 | jcfr | Note Added: 0009534 | |
2013-08-23 11:01 | nicole | Note Added: 0009571 | |
2013-08-23 11:01 | nicole | Category | Module Annotations => Module Markups |
2013-08-23 11:05 | nicole | Note Added: 0009572 | |
2013-08-30 10:53 | nicole | Note Added: 0009733 | |
2013-09-02 18:57 | jcfr | Target Version | Slicer 4.3.0 => Slicer 4.3.1 |
2013-09-24 12:44 | jcfr | Target Version | Slicer 4.3.1 => Slicer 4.3.2 |
2013-10-09 14:17 | nicole | Note Added: 0010170 | |
2013-10-10 11:41 | millerjv | Note Added: 0010171 | |
2013-10-14 06:25 | nicole | Note Added: 0010175 | |
2013-10-14 07:59 | nicole | Note Edited: 0010175 | |
2013-10-21 06:10 | jcfr | Fixed in Version | => Slicer 4.3.2 |
2013-10-21 06:11 | jcfr | Note Added: 0010203 | |
2014-03-06 10:15 | nicole | Target Version | Slicer 4.3.2 => Slicer 4.4.0 |
2014-03-06 10:17 | nicole | Fixed in Version | Slicer 4.3.2 => Slicer 4.4.0 |
2014-03-07 09:37 | pieper | Note Added: 0011360 | |
2014-05-13 10:33 | jcfr | Relationship added | related to 0003690 |
2014-05-13 10:34 | jcfr | Fixed in Version | Slicer 4.4.0 => |
2014-05-13 10:34 | jcfr | Target Version | Slicer 4.4.0 => |
2014-07-09 12:57 | nicole | Relationship added | related to 0003761 |
2014-07-11 04:41 | jcfr | Note Added: 0012160 | |
2014-07-11 04:51 | pieper | Note Added: 0012162 | |
2014-07-11 06:40 | nicole | Note Added: 0012167 | |
2014-07-12 16:34 | jcfr | Note Added: 0012172 | |
2014-12-20 17:41 | jcfr | Note Added: 0012797 | |
2015-11-03 13:51 | nicole | Note Added: 0013537 | |
2015-11-03 14:13 | jcfr | Note Added: 0013538 | |
2015-11-03 14:58 | nicole | Note Added: 0013539 | |
2015-11-04 06:49 | nicole | Note Added: 0013556 | |
2015-11-04 08:08 | nicole | Note Added: 0013559 | |
2015-11-11 13:13 | jcfr | Note Added: 0013595 | |
2017-06-07 23:27 | Changeset attached | => Slicer 2145-support-for-installing-extension-from-file d02e772f | |
2017-06-07 23:27 | Changeset attached | => Slicer 2145-support-for-installing-extension-from-file 15908f5b | |
2017-06-10 08:51 | jcfr | Changeset attached | => Slicer master 0a7c91eb |
2017-06-10 08:51 | jcfr | Changeset attached | => Slicer master 5bda82b9 |
2017-06-13 15:15 | lassoan | Note Added: 0014821 | |
2018-05-30 00:35 | lassoan | Target Version | => backlog |
2018-05-30 00:35 | lassoan | Note Added: 0015806 |