Difference between revisions of "Developer Meetings/20131029"
From Slicer Wiki
m (→Results) |
|||
| Line 13: | Line 13: | ||
Few options: | Few options: | ||
| − | * Avoid direct node observation by listening for the Scene. Node could have a pointer to the Scene so that they call "InvokeEvent" on the scene. | + | * Avoid direct node observation by listening for the Scene. Node could have a pointer to the Scene so that they call "InvokeEvent" on the scene. Widgets would then listen to the scene. |
* Investigate how the qMRMLSceneModel can be optimized so that one instance of the model is shared whenever possible. This would reduce the number of observations. | * Investigate how the qMRMLSceneModel can be optimized so that one instance of the model is shared whenever possible. This would reduce the number of observations. | ||
| + | |||
| + | HideFromEditor: | ||
| + | * Could be renamed into Internal | ||
| + | * Instead of associated the value with each node, this could be a property of the scene. | ||
Latest revision as of 20:42, 29 October 2013
Home < Developer Meetings < 20131029Contents
Attendees: Steve Pieper, Andriy Fedorov, Andras Lasso, Csaba Pinter, Kevin Wang, Ron Kikinis, Nicole Aucoin, Jc
To discuss
Results
Following today's discussion, we decided to go with OptionA described in here, it means that we would have to improve the performance of the MRML scene.
Few options:
- Avoid direct node observation by listening for the Scene. Node could have a pointer to the Scene so that they call "InvokeEvent" on the scene. Widgets would then listen to the scene.
- Investigate how the qMRMLSceneModel can be optimized so that one instance of the model is shared whenever possible. This would reduce the number of observations.
HideFromEditor:
- Could be renamed into Internal
- Instead of associated the value with each node, this could be a property of the scene.
