Skip to content

Conversation

@SludgePhD
Copy link
Contributor

Objective

  • Allow third-party code to integrate with winit MonitorHandles represented by bevy Monitor entities.

Solution

  • Reexport this resource type, just like WinitWindows.
  • It was already part of the public API through the system types.

Copy link
Contributor

@HugoPeters1024 HugoPeters1024 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As the creator of a third party rendering plugin for Bevy, I believe allowing superusers to hook into these kinds handles is very important! Thanks for the contribution 💪

I'd love to actually see an example that makes some kind of integrations directly on the winit layer, that way the bevy devs are reminded to keep those options in the public interface. But that's a separate issue.

@alice-i-cecile alice-i-cecile added this to the 0.17.3 milestone Nov 9, 2025
@alice-i-cecile alice-i-cecile added C-Bug An unexpected or incorrect behavior A-Windowing Platform-agnostic interface layer to run your app in S-Ready-For-Final-Review This PR has been approved by the community. It's ready for a maintainer to consider merging it labels Nov 9, 2025
@alice-i-cecile alice-i-cecile added this pull request to the merge queue Nov 9, 2025
Merged via the queue into bevyengine:main with commit dc22ec3 Nov 9, 2025
43 checks passed
mockersf pushed a commit that referenced this pull request Nov 17, 2025
# Objective

- Allow third-party code to integrate with winit `MonitorHandle`s
represented by bevy `Monitor` entities.

## Solution

- Reexport this resource type, just like `WinitWindows`.
- It was already part of the public API through the system types.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-Windowing Platform-agnostic interface layer to run your app in C-Bug An unexpected or incorrect behavior S-Ready-For-Final-Review This PR has been approved by the community. It's ready for a maintainer to consider merging it

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants