bug#72440: 31.0.50; MacOS: TUINSRemoteViewController log message

["Mattias Engdegård" <mattias.engdegard@gmail.com>]

5 aug. 2024 kl. 21.16 skrev Alan Third <alan@idiocy.org>:

> The correct thing to do is only set this when compiling on v14 or
> above, so the #ifdef is the right way to go.

Thanks, I pushed something that at least silenced the compiler, but please verify that I didn't break anything.

But should I worry about the property not being set on my machine? If I understand the release notes:

> In macOS 14, AppKit is exposing the clipsToBounds property of NSView.
> 
> For applications linked against the macOS 14 SDK, the default value of this property is true. Apps linked against older SDKs default to false. Some classes, like NSClipView, continue to default to true. The change in defaults recognizes that it is vastly easier to reason about clipping a view’s descendants than it is to unclip a view’s ancestors.
> 
> Users can turn clipping back on by using the NSView.clipsToBounds setter or using the attributes inspector of a view in the Xcode interface builder.
> This property is available back to macOS 10.9. This availability is intended to allow code targeting older OSes to set this property to true without guarding the setter in an availability check. Setting this property to false on previous OSes may not work reliably.

correctly, then the property exists in older versions but is just not exposed -- is that a correct interpretation? So attempting to set it might actually work, even though the compiler warns? If so, would it be possible to declare it manually to please the compiler?