I have done some experiments with this, but the changes would need more testing -- I don't see this happening in the RSNA timeframe.

I have uploaded two images. The top one shows the extent that I want, the bottom one shows the quality that I want. I do not have enough screen real estate to keep the sliceviewers at the size needed.

A kludge is as follows: choose red slice layout only, then switch to 3d viewer only layout. If the cross section displayed is the red viewer, I get my resolution.

Post RSNA is now. Using full resolution of the image data and inheriting only pan and zoom from the slice viewer should be the default. I have gotten several complaints about this in the meantime.

Alex is working on this - probably another week or so until he has a working version.

This functionality has been added some time ago. You can use FOV, Spacing matches volume option to display full size slice in 3D.

-what is missing is a fourth option: FOV match volume, spacing match 2D.
-Spacing matches volume is not interpolated. It should be by default. Interpolation is controlled in the pop up and by a check box in the volumes module. If I uncheck the check box in the volume module, the icon in the slice viewer pop up is not updated. See attached screenshot

Interpolation issue could be linked to 0001926, 0002682, 0001926, 0001935

How about that fourth option that I requested?

I traced interpolation issue to blocking Qt signals in the
qMRMLSliceControllerWidgetPrivate::updateWidgetFromMRMLSliceCompositeNode() method when a volume is loaded:

line 889:
// Update "foreground layer" node selector
wasBlocked = this->ForegroundComboBox->blockSignals(true);
this->ForegroundComboBox->setCurrentNode(
q->mrmlScene()->GetNodeByID(this->MRMLSliceCompositeNode->GetForegroundVolumeID()));
this->ForegroundComboBox->blockSignals(wasBlocked);

This prevents from setting observers on vtkMRMLVolumeDisplayNode in
qMRMLSliceControllerWidgetPrivate::onForegroundLayerNodeSelected(vtkMRMLNode * node) which is not called because of signal blockage.

I am not sure what the is the reason for blocking signals. Julien or JC could you comment on this?

As it is mentioned in 0001926, all those issues are due to: http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=19320
You might want to see with Jim.
I vote against using those blocksignals. I believe they are the root cause of the issues I listed in (0007635).

Additional information on my previous note:
if I change the code above to not block the signal, the interpolation button gets synced between different 2D view controllers and Volume module.

I will wait for Julien or JC to comment on this before committing my changes.

Take a look at the commit log that Julien identified.

The problem was that if you switched into the ViewControllers module, new controllers may be constructed and configured to match the scene. When these controllers are configured with the FG and BG images, they trigger all the callbacks. If linking is on, this can cause the content of the visible 2D Viewers to switch. Block signals addresses this issue. The basic problem is that we cannot tell when the ComboxBox is changed by the user or changed programmatically.

I think this commit predates the SliceLinkLogic which may be another way to handle the problem.

Jim, I am not sure I understand all the considerations related to linking but would the following addition to the code cause problems?:

// Update "foreground layer" node selector
wasBlocked = this->ForegroundComboBox->blockSignals(true);
this->ForegroundComboBox->setCurrentNode(
q->mrmlScene()->GetNodeByID(this->MRMLSliceCompositeNode->GetForegroundVolumeID()));
this->ForegroundComboBox->blockSignals(wasBlocked);
this->onForegroundLayerNodeSelected(q->mrmlScene()->GetNodeByID(this->MRMLSliceCompositeNode->GetForegroundVolumeID()));

Since the original issue is different from the "interpolation" sync problem, I created a separate issue:
http://na-mic.org/Mantis/view.php?id=3028
Please use it for farther communication.

Added FOV based on Volumes, resolution based on 2D View mode into reslice functionality. It is available in 2D slice controller widget pop-up.

http://viewvc.slicer.org/viewvc.cgi/Slicer4?view=revision&revision=21857