Skip to content

Conversation

@nicoburns
Copy link
Contributor

  • Tested on all platforms changed
  • Added an entry to the changelog module if knowledge of this change could be valuable to users
  • Updated documentation to reflect any user-facing changes, including notes of platform-specific behavior
  • Created or updated an example program if it would help users understand this functionality
  • Updated feature matrix, if new features were added or implemented

This is an alternative fix for #3958 which makes the fix within winit itself rather than in the window example like #3959. I think something like this is probably the better fix as it means that users don't all have to set the activation policy manually if they want keyboard support.

@nicoburns nicoburns requested a review from madsmtm as a code owner October 23, 2024 05:09
@purajit
Copy link
Contributor

purajit commented Oct 23, 2024

(As the author of #3920 that caused this) Thanks for doing this so quickly! Makes sense to me.

Copy link
Member

@madsmtm madsmtm left a comment

Choose a reason for hiding this comment

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

Ah, the difference between bundled and unbundled apps continue to be my bane!

@madsmtm madsmtm added B - bug Dang, that shouldn't have happened DS - appkit Affects the AppKit/macOS backend labels Oct 25, 2024
@madsmtm madsmtm linked an issue Oct 25, 2024 that may be closed by this pull request
@madsmtm madsmtm merged commit f6b2085 into rust-windowing:master Nov 18, 2024
58 checks passed
@madsmtm
Copy link
Member

madsmtm commented Nov 18, 2024

Thanks for fixing this!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

B - bug Dang, that shouldn't have happened DS - appkit Affects the AppKit/macOS backend

Development

Successfully merging this pull request may close these issues.

macOS: window example doesn't accept keyboard focus

4 participants