> By logging when init and viewDidMoveToWindow methods, you can see when the
> latter fails to be called.
That's what i did
> It's a bug Apple needs to fix.
Oh, it's a well-known bug?
Good to know.
> They broke it some time ago, then didn't fix it when the partially fixed
> legacy screensave
I’m seeing it failing on MacOS 10.5.5 on a 3 monitor system and in 13.2.1 on a
2 monitor system when compiled from source. And by “fail”, I mean that it only
runs on one display.
Alex Zavatone
> On Jun 12, 2023, at 7:23 AM, Steven Mills via Cocoa-dev
> wrote:
>
> On Jun 10, 2023, at 12:45,
On Jun 10, 2023, at 12:45, Gabriel Zachmann via Cocoa-dev
wrote:
>
> Two of the instances never reach method -viewDidMoveToWindow.
>
> Is there a way to instrument the source code or the executable, such that I
> can receive a line-by-line trace of the execution of the three screensaver
> ins
>
> I have one user, who has three displays connected to the Mac, but only the
> main display (center) gets a screensaver.
> This is on macOS Ventura 13.4.
> (I should also say that with other users, who also have multiple displays,
> everything seems fine.)
>
> According to the log file, legacy
I have a screensaver that is supposed to run on all displays simultaneously.
MacOS launches several instances, if there are multiple displays.
I have one user, who has three displays connected to the Mac, but only the main
display (center) gets a screensaver.
This is on macOS Ventura 13.4.
(I sho
