RemoteView `still_ratio` is not used initially about trame-vtk HOT 6 CLOSED

Ah that is interesting. That still_ratio was not really meant to be go beyond 1 (at least initially).

I guess, I just need to look at the code path to make sure things get set in the right order... ;-)

from trame-vtk.

Usually you want the window to match the space available not make it bigger. But there is nothing wrong to bump the resolution beyond the space you have available.

Anyway, I'm not saying we should not support number more than 1, but at least that is where it is coming from and why we always start with 1.

from trame-vtk.

I mean there is no technical issue here. I was just explaining the history and the why.

from trame-vtk.

That still_ratio was not really meant to be go beyond 1 (at least initially).

Really? I'm using values of 2 and even up to 4 regularly to add "crispness" to the image

from trame-vtk.

Makes sense. I'm wondering if vtkWindowToImageFilter and its SetScale() should be used if the ratio/scale is greater than 1?

from trame-vtk.

That would not work because the scale in vtkWindowToImageFilter is an integer.

from trame-vtk.