Twitter | Search | |
Peter Steinberger Nov 6
“Cannot update for observer <NSKeyValueObservance> for the key path "screen.visibleFrame" from <UINSWindow>, most likely because the value for the key "screen" has changed without an appropriate KVO notification being sent. Check the KVO-compliance of the UINSWindow class.” 🙃
Reply Retweet Like
Peter Steinberger Nov 6
Replying to @steipete
Is NSKeyValueNestedProperty a Swift thing? I’m just using KVC and don’t understand why observing is set up.
Reply Retweet Like
Peter Steinberger
Hunted this down for hours, turns out Catalyst throws that if you set a frame that’s too small for an NSWindow. ffs. Why are these frameworks so bad. Could have just asserted or logged or thrown an exception complaining about size.
Reply Retweet Like More
Evgeny Khodykin Nov 6
Replying to @steipete
To be honest, reading of all these problems, it looks like a native AppKit application would be less painful than this Catalyst cavalcade.
Reply Retweet Like
Peter Steinberger Nov 6
Replying to @ekhodykin
Then I’d complain way more about AppKit. 🙃
Reply Retweet Like
Iulian Onofrei Nov 6
Replying to @steipete
I once found a method that received a nullable error reference, but if you passed nil to ignore errors, it crashed instead.
Reply Retweet Like
Peter Steinberger Nov 6
Replying to @Revolt666
That’s fairly common tbh
Reply Retweet Like
James F Hanshaw Nov 6
Replying to @steipete
And this was supposed to be v2.0 based on last year being 1.0 but it’s more like that was .5 instead 🤷‍♂️🤷‍♂️
Reply Retweet Like
ePirat Nov 6
Replying to @steipete
Oh god… Reminds me of the xip tool claiming the .xip is not from Apple, when in fact it is and just the signature cert expired…
Reply Retweet Like