You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is as currently intended: The slicer works in local (voxel) coordinates of the (first) volume dataset.
It would be a good idea to redesign the slicer to work based on global coordinates; this would require some UI redesign as well, since the current slice numbers (given in voxel coordinates of the first dataset) aren't really helpful in a global context.
The position of the dataset in the slicer is not updated, when the dataset position is update manually.
The text was updated successfully, but these errors were encountered: