Mads Marquart
Mads Marquart
> I haven't exactly followed this PR, but how is this "surface inside window" representation going to come together with #3942 and all future "subsurface" changes that we're going to...
I have changed `fn safe_area` to return the insets (`dpi::PhysicalInsets { top, left, bottom, right }`) instead, since I belive that will be more forwards-compatible with https://github.com/rust-windowing/winit/issues/3911 and other improvements...
I've merged this now, though note that it's only really implemented for macOS and iOS (and Wayland, because there's no protocol for it). Web is implemented, though as noted above,...
> Would this suggestion be an issue due to #3406? Yes, though in practice Imma be fixing that
Hmm, I think I may be wrong on how these things work, converting to draft for now
Related to https://github.com/rust-windowing/winit/issues/783.
Thanks for the detailed investigation! You are right that we should be using `respondsToSelector:` - and in the future, [`objc2::available!`](https://github.com/madsmtm/objc2/blob/d1d470f699c131d5855574ca49695659aa03dc59/crates/objc2/src/macros/available.rs#L118) (once I release the next version) to select the new...
The answer is yes to both ;)
I've opened https://github.com/rust-windowing/winit/issues/4034 for using the documented cursors
Hmm, while #1103 does improve this situation, it does not really address the underlying issue of **the C compiler itself** using these variables. What I mean is that it only...