Tracking issue: Sizing(&mut PhysicalSize) event

[Osspial]

As discussed in #695 (comment). This will address #584 and allow window resize increments (useful for text editors).

Any PR that implements this should expose the client area's size, not the external window size.

[elinorbgr]

Might be worth thinking if / how it should fit with the optional suggested size of the HiDPIFactorChanged event I suggested in #837 (comment) maybe?

[goddessfreya]

@Osspial Is this still relevant?

[Osspial]

@zegentzy Yeah, this was the original version of #949. I'd rather use this issue, since it's more specific about the sort of design we're looking for.

[LoganDark]

Any progress / news on this? It's been over a year, and this would be very useful. Right now you can only set a 'resize increment' once and only on specific platforms.

[madsmtm]

Since #2411 we now have Window::set_resize_increments, and it works with the client area's size.

While that doesn't fully address the original suggestion (having a callback on resize that the user can then respond to), I think it should solve the primary use-case? If not, feel free to reopen.

[LoganDark]

@madsmtm Does winit already fill the other use cases for a resize callback, such as aspect ratio constraints?

[madsmtm]

I don't think so, but perhaps that use-case (aspect ratio constraints) is more appropriately tracked in #584?