---
# System prepended metadata

title: Winit meeting 2024-02-23

---

# Winit meeting

Date: 2024-02-23T15:00:00Z (UTC)

Attended: @daxpedda, @notgull, @madsmtm, @kchibisov

Last meeting notes: <https://hackmd.io/Xy9ZdqNPTQCtACQwdXtwWw>


## Status update on iOS (@madsmtm)

I've been working on improving `rustc`'s Mac Catalyst support, and in general the Rust + iOS workflow and debugging experience. I am kinda warming up to UIKit, will probably be expanding the iOS implementation a lot in a few months once `icrate` can generate UIKit headers.


## ApplicationHandler

Previously: https://github.com/rust-windowing/winit/pull/3386

Now: https://github.com/rust-windowing/winit/pull/3517


## Subsurfaces

https://github.com/rust-windowing/winit/issues/3506

We can route mouse input.

Keyboard input needs focus. Maybe we re-implement focusing? Definitely need some sort of platform-specific focusing.

Event bubbling? Some things maybe cannot bubble (popups). Has to be user-controllable.


## DPI

https://github.com/rust-windowing/winit/issues/3433

Does `glutin`/`softbuffer` want a `dpi` crate? They probably wouldn't really use it.

Would probably need some rework to make it usable generally.


## Unreleased changelog

https://github.com/rust-windowing/winit/pull/3496

When releasing, we have to do something about the unreleased changes. @madsmtm has ideas.


## Lockfile

https://github.com/rust-windowing/winit/issues/3085

@madsmtm is leaning towards committing it, and then setting up Dependabot.

Lockfile for MSRV (maybe called `Cargo-MSRV.lock`?), generated using Cargo's `-Zminimal-versions`, run `cargo update` for not MSRV because we want to test against latest versions.


## Gamepad

https://github.com/rust-windowing/winit/pull/3450

How do we want to proceed with gamepad?

Postpone to next meeting, we each need to research for our own backends.


## Cute Logo

Do we want a cute animal logo for `rust-windowing`?

@madsmtm: I love the current one.
@daxpedda: I don't mind if someone wants to create a "better" one.


## Loose thoughts about Window creation

`Window` doesn't need to be destroyed in `Suspended` and recreated in `Resumed`, only the surface should. An API that provides easy initialization handling is immensely valuable!

I think, at least, still not quite sure how this sort of stuff works on Android.
