Re: [ferret_users] Frame only save upper left portion of an image

[William Kessler <william.s.kessler@xxxxxxxx>]

This has been discussed here recently. See Ryo's post quoted below from 16 July. 
Unfortunately the cropping depends on the monitor resolution: not easy to change! 
But your message suggests that it also depends on the IOS and/or PyFerret version. Can you tell which it was? (i.e. did you also update your OS? Or your monitor?)

Billy

> On Sep 22, 2021, at 10:32 AM, Gopika Suresh <gopikasurvay@xxxxxxxxx> wrote:
> 
> Dear users,
> 
> I have updated my pyferret version in my system recently. I am using the IOS Big sur 11.5.1 version. After updating, using the frame command my ferret is saving only a portion of the plot. Are there any fixes available?
> 
> Thanks in advance
> Gopika.s
> 
> -- 
> Gopz



Begin forwarded message:

> From: Ryo Furue <furue@xxxxxxxxxx>
> Subject: [ferret_users] Mac, PyFerret, FRAME, image is cropped
> Date: July 16, 2021 at 12:57:18 AM PDT
> To: ferret users <ferret_users@xxxxxxxx>
> 
> Dear Mac-PyFerret users,
> 
> If you use PyFerret on Mac, do you get correct images from the FRAME command used interactively?  (Let's assume we all use the latest version of PyFerret.)
> 
> As has been reported several times on this mailing list, an image saved with the FRAME command
> 
> ! . . . plot something . . .
> frame/file=theimage.png
> 
> saves only the upper-left portion of the plot even though this plot is correctly displayed on the screen.
> 
> Billy (Kessler), Wei (Cheng), and I have been talking about this issue.  Billy and I have the problem but Wei doesn't.  Why?
> 
> It turns out that the hardware matters:  The results depend on the computer monitor.
> 
> Wei usually uses an external monitor, which doesn't cause the problem, but when she switched to her laptop's builtin monitor, she was able to reproduce the problem.
> 
> Also, Billy discovered that as he lowered the screen resolution of the monitor ("System Preferences" > "Display"), more portion of the image was captured by the FRAME command.
> 
> So, we suspect that the bug is
> - in the graphics driver(s), or
> - in how Qt uses the graphics drivers, or
> - in how PyFerret uses Qt.
> 
> I hope somebody is able to fix it.
> 
> In the meantime, the available workarounds include
> 
> - use PyFerret in the non-interactive mode: "pyferret -nodisplay -script yourscript.jnl"
> - find a "suitable" external monitor.
> - lower the screen resolution.
> 
> Best regards,
> 
> Ryo
>