Robert Bragg

> For native apps then I'd generally expect you'd want to list _all_ the flags that are relevant to your app. also this is probably too much of an over...

yeah, it seems pretty safe to say that basically all native apps would want those listed in `android:configChanges` but maybe some of the other ones make sense to consider on...

I think supporting them both just helps demonstrate a path away from only supporting NativeActivity which I'd say is more the focus (at least that's why I ended up looking...

> > because many people have the impression they will be able to develop 100% Rust applications, considering that it's distributed as part of the platform. (imho a misconception) >...

Reviewing some of the outstanding PRs / issues for x11 I also couldn't help but notice this [mammoth series](https://github.com/rust-windowing/winit/pull/2088) which includes full integration of XInput2 and libxkbcommon (definitely a good...

At least in terms of the description of the issue given, and the proposed fix this seems like a reasonable workaround. I mean it's kinda terrible to have this kind...

@ArturKovacs it looks like that work was essentially to integrate more deeply with XIM so that pre-edit events from the XIM server could be translated into platform-independent Winit events.

The tricky thing with porting from xlib to xcb is that xlib does more than just wrap the wire protocol, it also includes various utilities, with the most notable here...

It looks like there's loads of really good work buried in this series - though it's a bit surprising how long of a series of changes this is stacked on...

> Like I said in the OP, for this PR only the last two commits are relevant. The remaining commits are part of the linked PR. Yeah, although I'd seen...