This is a step in the right direction, but why is this a dev-dep still?

Because testing needs to initialize ManualTextureViews for some reason, dunno.

Depends on #20506

This is a step in the right direction, but why is this a dev-dep still?

Because testing needs to initialize ManualTextureViews for some reason, dunno.

It's just needed for the camera updates, I made a quick PR at #20512 that simplifies the UI test setup and removes the need for it.

thanks for looking into that @ickshonpe ! i have been wondering if we want to move as much of camera_system's logic into bevy_camera as we can, and leave just a lil bit of it in bevy_render for resizing render target or whatever has to happen. Then we wouldnt need a test specific setup hopefully

thanks for looking into that @ickshonpe ! i have been wondering if we want to move as much of camera_system's logic into bevy_camera as we can, and leave just a lil bit of it in bevy_render for resizing render target or whatever has to happen. Then we wouldnt need a test specific setup hopefully

For layout bevy_ui is almost there already. All the window and camera queries are in update_ui_context_system which collects the details (just id, size and scale factor) of the UI render targets and then propagates them via the ComputedNodeTarget component. Then the text, layout and widget systems just query for ComputedNodeTarget and don't need to know anything else. The exception is picking which is still a bit of a mess.