View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0003197 | Slicer4 | Core: MRML | public | 2013-06-26 10:30 | 2016-06-17 11:53 |
Reporter | kotwicz | Assigned To | hastings.greer | ||
Priority | normal | Severity | minor | Reproducibility | always |
Status | resolved | Resolution | no change required | ||
Product Version | Slicer 4.2.0 | ||||
Target Version | Fixed in Version | ||||
Summary | 0003197: Camera rotation issue | ||||
Description | -- type the following in the python interactor further calls don't rotate camera as expected.camera.Elevation(20) | ||||
Tags | No tags attached. | ||||
This is the intended behavior of vtkCamera.Elevation. It does not change the direction of vtkCamera.ViewUp, and so when the camera direction passes through ViewUp, the direction of "up" changes. The advantage of not changing viewUp is that the model stays right-side up, preventing disorientation. If you want viewUp to change for your use case, call vtkCamera.OrthogonalizeViewUp() after each call to vtkCamera.Elevation(), or use vtkMRMLCameraNode::RotateAround() |
|
Date Modified | Username | Field | Change |
---|---|---|---|
2013-06-26 10:30 | kotwicz | New Issue | |
2013-06-26 10:30 | kotwicz | Status | new => assigned |
2013-06-26 10:30 | kotwicz | Assigned To | => alexy |
2016-06-14 15:27 | jcfr | Assigned To | alexy => hastings.greer |
2016-06-14 16:11 | hastings.greer | Note Added: 0013972 | |
2016-06-14 16:17 | hastings.greer | Note Edited: 0013972 | View Revisions |
2016-06-14 16:42 | hastings.greer | Note Edited: 0013972 | View Revisions |
2016-06-16 10:02 | hastings.greer | Note Edited: 0013972 | View Revisions |
2016-06-16 10:34 | hastings.greer | Note Edited: 0013972 | View Revisions |
2016-06-16 10:38 | hastings.greer | Note Edited: 0013972 | View Revisions |
2016-06-17 11:53 | hastings.greer | Status | assigned => resolved |
2016-06-17 11:53 | hastings.greer | Resolution | open => no change required |