Skip to content

Version 0.17 -- update to support winit 0.30 - #66

Closed
mrfoogles wants to merge 4 commits into
rukai:mainfrom
mrfoogles:main
Closed

Version 0.17 -- update to support winit 0.30#66
mrfoogles wants to merge 4 commits into
rukai:mainfrom
mrfoogles:main

Conversation

@mrfoogles

Copy link
Copy Markdown
Contributor

Pretty much everything is done and it seems to work except I don't know how to update the one example for the web, because I can't find the docs. The OS repeating key detection seems to detect the E key as OS repeating whether it is or not (Mac M3), but I assume it did that before as I don't think I changed anything related to that. Also updated the guidance on when to render. This is probably most of the work I'm planning to do, although I wouldn't mind fixing a typo or something (although you can probably do that yourself).

@mrfoogles

mrfoogles commented Mar 21, 2025

Copy link
Copy Markdown
Contributor Author

Fixes #60.

@mrfoogles mrfoogles mentioned this pull request Mar 21, 2025
3 tasks
…ust calling them manually, as another update pull request does -- it's the same thing
Comment thread src/winit_input_helper.rs
/// You should now run your application logic, calling any of the accessor methods you need.
/// Call `WinitInputHelper::process_window_event()` for every window event you recieve in ApplicationHandler.window_event()
/// Call `WinitInputHelper::process_device_event()` every time ApplicationHandler.device_event() is called.
/// Call `WinitInputHelper::process_new_events()` every time ApplicationHandler.new_events() is called.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Function does not exist. WinitInputHelper::step()?

Comment thread src/winit_input_helper.rs
/// Call `WinitInputHelper::process_window_event()` for every window event you recieve in ApplicationHandler.window_event()
/// Call `WinitInputHelper::process_device_event()` every time ApplicationHandler.device_event() is called.
/// Call `WinitInputHelper::process_new_events()` every time ApplicationHandler.new_events() is called.
/// Call `WinitInputHelper::process_about_to_wait()` every time ApplicationHandler.about_to_wait() is called.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

end_step?

Comment thread changelog.md

The recommendations this crate gives about where to render and run your application logic have also been updated to match new guidance.
As update() has been removed, it no longer returns true when you should run application logic. Instead, run your application logic _after_ calling .process_about_to_wait() in ApplicationHandler::about_to_wait().
Run rendering code in ApplicationHandler::window_event() only when .process_window_event() returns true, indicating it received a RequestedRedraw event. It doesn't care about which window was requested to be redrawn, but if you do, you'll have to handle it yourself. If you want to render every frame, remember to call Window::request_redraw() in ApplicationHandler::about_to_wait() every time.

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Functions process_new_events and process_about_to_wait seem to have been renamed to step and end_step

This was referenced Sep 18, 2025
@rukai

rukai commented Sep 18, 2025

Copy link
Copy Markdown
Owner

Many thanks for your work on this, I have completed the move to winit 0.30.0 here: #68

@rukai rukai closed this Sep 18, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants