Difference between revisions of "Projects:ARRA:miAnnotation Meeting 07202010"
From NAMIC Wiki
| (6 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| − | [[Projects:ARRA:miAnnotation|Back to miAnnotation page]] | + | [[Projects:ARRA:miAnnotation#Progress|Back to miAnnotation page]] |
= Agenda = | = Agenda = | ||
== Hierarchy nodes concept == | == Hierarchy nodes concept == | ||
| − | * introducing the hierarchy nodes concept (known from the model module in | + | * introducing the hierarchy nodes concept (known from the model module in Slicer3) to group annotations |
| − | Slicer3) to group annotations | ||
** enables to work on all annotations of one type or one subset | ** enables to work on all annotations of one type or one subset | ||
** Nicole provides architecture | ** Nicole provides architecture | ||
| Line 11: | Line 10: | ||
*** fiducial lists are def. needed | *** fiducial lists are def. needed | ||
*** goes along with the hierarchy | *** goes along with the hierarchy | ||
| − | *** able to hide all of one type, work on just one type, show all but work | + | *** able to hide all of one type, work on just one type, show all but work on one type |
| − | on one type | + | *** in the GUI sublists in the list widget would enable to select either a list or single annotations |
| − | *** in the GUI sublists in the list widget would enable to select either a | ||
| − | list or single annotations | ||
* display annotation position (coordinates) in the list? | * display annotation position (coordinates) in the list? | ||
* every annotation has to have a display node | * every annotation has to have a display node | ||
| Line 22: | Line 19: | ||
== VTK widget testing macros == | == VTK widget testing macros == | ||
| − | * vtk widget testing macros to check if the widgets provide the | + | * vtk widget testing macros to check if the widgets provide the functionality we want them to (Nicole) |
| − | functionality we want them to (Nicole) | + | **[[Projects:ARRA:VTKWidgetsTesting | VTK Widgets Testing Notes]] |
== Displayable manager active node concept == | == Displayable manager active node concept == | ||
| Line 29: | Line 26: | ||
* displayable manager active node concept | * displayable manager active node concept | ||
** no asserts in the code, will kill slicer | ** no asserts in the code, will kill slicer | ||
| − | ** solutions for multiple 3D views | + | ** solutions for multiple 2D/3D views |
*** MRMLViewNode should have IsCloneOf(viewId ..) ? | *** MRMLViewNode should have IsCloneOf(viewId ..) ? | ||
| − | |||
| − | |||
**** rename ActiveTag in cameraNode to associatedView or activeView | **** rename ActiveTag in cameraNode to associatedView or activeView | ||
| − | *** enable to | + | *** We would like to enable to view different annotations for different views |
| + | **** Every DisplayNode has a DeactiveTagList | ||
| + | **** A Tag is added to the DeactiveTagList if the node should not be displayed in the viewer | ||
| + | **** If a new viewer is created the corresponding displayableManager inserts all those widgets in that viewer that do not have the tag of that viewer in the DeactiveTagList of corresponding DisplayNodes | ||
*** what happens if a scene containing annotations is loaded? | *** what happens if a scene containing annotations is loaded? | ||
| − | *** MRMLViewNode::GetActive() to create the annotations in the appropriate | + | *** MRMLViewNode::GetActive() to create the annotations in the appropriate 3D view |
| − | 3D view | + | |
| + | = Resources = | ||
| + | {| | ||
| + | |[[Image:Projects-ARRA-miAnnotation_Picture_of_whiteboard_at_meeting_with_Nicole_and_Steve.jpg|thumb|center|Meeting with Nicole and Steve - July 19th, 2010|300px]] | ||
| + | |} | ||
Latest revision as of 18:15, 29 July 2010
Home < Projects:ARRA:miAnnotation Meeting 07202010Contents
Agenda
Hierarchy nodes concept
- introducing the hierarchy nodes concept (known from the model module in Slicer3) to group annotations
- enables to work on all annotations of one type or one subset
- Nicole provides architecture
- annotation lists for all annotation types? (see attached picture)
- fiducial lists are def. needed
- goes along with the hierarchy
- able to hide all of one type, work on just one type, show all but work on one type
- in the GUI sublists in the list widget would enable to select either a list or single annotations
- display annotation position (coordinates) in the list?
- every annotation has to have a display node
- includes getters/setters for visibility, colors
- where should the lock functionality go?
- does lock mean no position change or no change at all
VTK widget testing macros
- vtk widget testing macros to check if the widgets provide the functionality we want them to (Nicole)
Displayable manager active node concept
- displayable manager active node concept
- no asserts in the code, will kill slicer
- solutions for multiple 2D/3D views
- MRMLViewNode should have IsCloneOf(viewId ..) ?
- rename ActiveTag in cameraNode to associatedView or activeView
- We would like to enable to view different annotations for different views
- Every DisplayNode has a DeactiveTagList
- A Tag is added to the DeactiveTagList if the node should not be displayed in the viewer
- If a new viewer is created the corresponding displayableManager inserts all those widgets in that viewer that do not have the tag of that viewer in the DeactiveTagList of corresponding DisplayNodes
- what happens if a scene containing annotations is loaded?
- MRMLViewNode::GetActive() to create the annotations in the appropriate 3D view
- MRMLViewNode should have IsCloneOf(viewId ..) ?
