weird startup scaling issues on macOS after winit `0.30`

[tychedelia]

See video here:

window.mp4

This probably doesn't need to be blocking for 0.14 but feels pretty gross.

[rparrett]

It seems like the initial render is at scale_factor 1.0 and updates to the correct scale factor on the next frame.

[rparrett]

No surprise, but bisected to #13366

[alice-i-cecile]

Yeah, strongly suspect we're not setting the initial value correctly. If y'all can figure out a fix, ping me and I'll merge it for 0.14.

[rparrett]

I think that what is generally going on is:

• We ask winit to create a window. We have no way of knowing what the scale factor is yet if we didn't override it.
• winit creates it and sends a resize event with the correct size / scale factor
• we don't respond to that event until a frame later.

I am not sure if this needs to be split off into a separate issue yet (will try to test on another platform), but I am also seeing scale_factor_override not yielding the correct window size. edit: this seems mac specific and probably related.

Adding

primary_window: Some(Window {
    resolution:
        bevy::window::WindowResolution::default().with_scale_factor_override(2.0), // something not-1.0
    ..default()
}),

Results in fonts becoming larger, but the window stays the same size. (forever, it never gets resized)