The table here looks wrong: <https://www.jetbrains.com/help/kotlin-multiplatform-dev/compose-lifecyc...

# compose-desktop

[Sean Proctor]

The table here looks wrong: https://www.jetbrains.com/help/kotlin-multiplatform-dev/compose-lifecycle.html#desktop
I didn't investigate the actual behavior, but it seems like windowGainedFocus should trigger ON_RESUME, not ON_PAUSE.

[Pablichjenkov]

Seems that it should also change the transition from Started -> Resumed

[Pablichjenkov]

The row below seems wrong too.

[zsmb]

Indeed, I have a PR open for this here https://github.com/JetBrains/kotlin-multiplatform-dev-docs/pull/109

[Alex Vanyo]

Does that mean that in desktop, only one window will be resumed at a time?

[zsmb]

That's the idea so far, but I think we're open for feedback on these bindings across all the platforms.

[Alex Vanyo]

With multi-resume more than one Activity can be resumed at the same time, but then there’s also a related onTopResumedActivityChanged callback for which one is “most” resumed.

[zsmb]

That's true, I actually have quite some trouble these days getting an Activity into a STARTED state at all these days...

[Marcin Wisniowski]

Fun fact, on Linux X11 has a little known feature to have 2 (or more) independent sets of mice and keyboard, with their own on-screen pointers. This results in each cursor having it’s own focus, and in turn multiple windows being able to be focused at the same time, and typed into at the same time (with 2 separate keyboards). This is mostly useful for multi-user systems using the same desktop session. (2 desks and sets of peripherals, same computer and desktop session)

[Alex Vanyo]

That’s amazing and quite an edge case. If you could do that on Android the entire focus system and input system might just immediately break