# 2021.01.26 Hangout
**URL:** https://discourse.slicer.org/t/2021-01-26-hangout/15658
**Category:** Weekly meetings
**Created:** [January 25, 2021, 5:28pm UTC](https://discourse.slicer.org/t/2021-01-26-hangout/15658 "2021-01-25T17:28:15Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@Sam\_Horvath](https://discourse.slicer.org/u/Sam_Horvath)
#### Post date: [January 25, 2021, 5:28pm UTC](https://discourse.slicer.org/t/2021-01-26-hangout/15658/1 "2021-01-25T17:28:15Z")
Tomorrow, we will be having our next weekly hangout at 10:00 AM ET until 11 AM ET.
Anyone is welcome to join to ask questions at [https://bit.ly/slicer-googlemeet-hosted-by-kitware](https://bit.ly/slicer-googlemeet-hosted-by-kitware)
Agenda:
- Discuss [Pluggable Markups Slicer#5349](https://github.com/Slicer/Slicer/pull/5349)
- Questions and comments related to cleanup of view initialization pipeline (see details in replies)
- Should `hotLinkedControl` property of `vtkMRMLSliceCompositeNode` be serialized ?
- Should we continue to support the camera module to synchronize view ?
- After integrating the corresponding topic, loading scene will always copy camera and we will remove the data loading option, is there any concern ?
- `vtkCameraNode::GetActiveTag()` will be deprecated in favor of a new function `vtkCameraNode::SetLayoutName()`
- Discuss approach to support interactive Slice intersection:
- The idea is two have functionality equivalent to what is implemented by `vtkResliceCursorThickLineRepresentation/vtkResliceCursorLineRepresentation` and `vtkResliceCursorWidget`
- Options:
- Update current intersection to optionally be interactive
- Leverage the plane widget so that intersection in Slice view can be interactive
- Add a displayable manager integrating the existing VTK widgets
- Review short presentation of Slicer to the [CSBC](https://csbconsortium.org/) imaging working group
- Slicer 5 and VTK9
Feel free to post to this thread to request/suggest a topic!
Thanks
Sam and J-Christophe
---
### Author:  [@pieper](https://discourse.slicer.org/u/pieper)
#### Post date: [January 26, 2021, 2:48pm UTC](https://discourse.slicer.org/t/2021-01-26-hangout/15658/2 "2021-01-26T14:48:27Z")
I’m giving a short presentation of Slicer to the [CSBC](https://csbconsortium.org/) imaging working group this afternoon. Here are the slides in case we have time to discuss during the hangout.
[https://docs.google.com/presentation/d/1grPMGPHnPRr1NSi2Mij4Uu2Fk\_72wNJZOIaM4b6WZZw/edit?usp=sharing](https://docs.google.com/presentation/d/1grPMGPHnPRr1NSi2Mij4Uu2Fk_72wNJZOIaM4b6WZZw/edit?usp=sharing)
---
### Author:  [@jcfr](https://discourse.slicer.org/u/jcfr)
#### Post date: [January 26, 2021, 2:54pm UTC](https://discourse.slicer.org/t/2021-01-26-hangout/15658/3 "2021-01-26T14:54:04Z")
Question related to cleanup of view initialization pipeline
- While working on integrating topic [lassoan/SlicerGitSVNArchive@cleanup-view-widget-creation2](https://github.com/lassoan/SlicerGitSVNArchive/tree/cleanup-view-widget-creation2), I observed inconsistency in the implementations of [WriteXML](https://github.com/Slicer/Slicer/blob/e0b9f1fb6af0653d92ce659e1c22e634f6965167/Libs/MRML/Core/vtkMRMLSliceCompositeNode.cxx#L74-L131) and [ReadXMLAttributes](https://github.com/Slicer/Slicer/blob/e0b9f1fb6af0653d92ce659e1c22e634f6965167/Libs/MRML/Core/vtkMRMLSliceCompositeNode.cxx#L273-L276) in `vtkMRMLSliceCompositeNode`, the `hotLinkedControl` property is never written to XML.
Is that an omission or should we remove it ?
---
### Author:  [@pieper](https://discourse.slicer.org/u/pieper)
#### Post date: [January 26, 2021, 2:55pm UTC](https://discourse.slicer.org/t/2021-01-26-hangout/15658/4 "2021-01-26T14:55:36Z")
> [@jcfr](#):
>
> `hotLinkedControl` property is never written to XML.
> Is that an omission or should we remove it ?
I’ve noticed that this isn’t persisted but didn’t look into fixing it. It would be really great to add this to the xml.
---
### Author:  [@jcfr](https://discourse.slicer.org/u/jcfr)
#### Post date: [January 26, 2021, 3:07pm UTC](https://discourse.slicer.org/t/2021-01-26-hangout/15658/5 "2021-01-26T15:07:30Z")
> [@jcfr](#):
>
> Question related to cleanup of view initialization pipeline
After rebasing the topic and consolidating it with lost changes from a previous version of the topic [cleanup-view-widget-creation1](https://github.com/lassoan/SlicerGitSVNArchive/tree/cleanup-view-widget-creation1), I did some testing and it looks promising 👍
While testing the Camera module, I noticed that assigning the same camera to two views is not working:
- Is it something we should fix ?
- Or should we instead (a) suggest developer to explicit sync camera node writing code and (2) remove the camera module?