![]() This must return the set of allowed NSExtensionItem payload classes. ![]() ![]() The extension point's NSExtensionContext subclass must implement `+_allowedItemPayloadClasses`. I'll try to double check by changing resolution.ĮrrorĐ9:49:11.053147-0800ĜoreFoundation ScreenSaverEngineĚttempt to load executable of a type that cannot be dynamically loaded for CFBundle 0圆0000103a000 (executable, not loaded)ĮrrorĐ9:49:11.056956-0800ĞxtensionFoundation ScreenSaverEngineĞxtension request contains input items but the extension point does not specify a set of allowed payload classes. So I think you're correct here, for some reason in some cases, the main screen thread's NSView is mistakenly put on the second monitor. This does not do anything for me, it doesn't replace the first one for example.Īgain coordinates are correct, but the view is not displayed where it should despite what it says. 18:40:40.967 : forcing startAnimation (workaround Ventura 13.3beta The workaround does kick in for the secondary monitor : But we know it shows up on the secondary despite correct frame and bounds. ![]() Now, this is the startAnimation that goes through : 18:40:39.922 : AerialView setup init (V3.2.4) preview: falseĠx139922a60 : This is the second screen, correct coordinates here 18:40:39.753 : AerialView setup init (V3.2.4) preview: falseĠx13f13cd60 : This is the init on main screen Ok so, I tried your idea for a workaround but I think that the original issue that you noted is not allowing us to fix it ourselves : So yeah, there's a good chance your workaround could actually work, I'll see if I can give it a shot quickly, it's likely you got the root cause here. This is however what I get with a more failed on first monitor launch : Regarding startAnimation, this was on a run where it launched correctly on both : I don't seem to see an offset although maybe there's one and I didn't notice it with the videos. So at least here I can correctly match to the monitor informations. (this is one 5K monitor and one 2560x 1440 monitor, so retina factor 2 and 1 respectively) I can't say I'm seeing this here, I get the correct coordinates passed in the init at least : I was having a second look, more precisely this part of your message :Īctual behavior: the screen’s rectangle seems to be offset by about 100 pixels (as if the NSView is not set to the actual screen coordinates)
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |