View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0004338 | Slicer4 | Core: MRML | public | 2017-02-03 12:08 | 2017-10-18 01:18 |
Reporter | johan.andruejol | Assigned To | alexy | ||
Priority | normal | Severity | feature | Reproducibility | N/A |
Status | assigned | Resolution | open | ||
Product Version | Slicer 4.7.0 | ||||
Target Version | backlog | Fixed in Version | |||
Summary | 0004338: Node should be notified they are being referenced/unreferenced | ||||
Description | As of now, it is possible to catch event whenever you add/modify/remove a reference on a node. The problem is that this event is only sent on the node that starts/modifies/ends the referencing. It would be great if the referenced node also got notifications that it's being referenced/unreferenced. | ||||
Steps To Reproduce | Example: Ideally, the transform node would also receive an event (NodeReferencedEvent/NodeUnReferencedEvent ?) it could act on. | ||||
Tags | No tags attached. | ||||
The motivation for this is the transform's module interaction widget extent update: when a transformable is added under a transform node, the interaction widget's bounding box needs to be updated. However, the transform node doesn't know when a transformable node sets it as its parent. The current implementation requires the user to manually reset the bounding box, which is not too bad (sometimes it is good that the bounding box is only recomputed on request). |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2017-02-03 12:08 | johan.andruejol | New Issue | |
2017-02-03 12:08 | johan.andruejol | Status | new => assigned |
2017-02-03 12:08 | johan.andruejol | Assigned To | => alexy |
2017-06-16 20:50 | lassoan | Note Added: 0014901 | |
2017-10-18 01:18 | jcfr | Product Version | Slicer 4.8.1 => Slicer 4.7.0 |
2017-10-18 01:18 | jcfr | Target Version | Slicer 4.8.1 => backlog |