Crash when mixing with JavaFx coroutines about compose-multiplatform

[pacher]

So, there is no need to waste time on fixing this.

Please do waste time on fixing this.
I just saw the announcement and will start to migrate to Compose from JavaFx today. But it can not be all done in once, there will be things missing etc. So Compose and JavaFx will co-exist for quite some time for me (I am planning to have JavaFx in different pop-up windows)

And anyway it is quite puzzling to me how is the simple presence of different dispatcher can cause an issue. What if I want to write or use other non-standard dispatchers? What causes the issue? What to look out for?

[olonho]

@igordmn IIRC you had simple fix with more explicit dispatcher selector. Can we apply it and check if it helps?

[pacher]

Wild guess: just find and replace Dispatchers.Main with Dispatchers.Swing in compose codebase?

[olonho]

Interesting problem, seems Swing (used by Compose) and JavaFX coroutine dispatchers cannot coexist. So not sure, if such a config is supported. Is it possible to not use JFX coroutine dispatcher?

[dector]

Not a major issue for me TBH - I was going to rewrite JavaFX granulary but now I'll just write Compose GUI as a separate app.

So, there is no need to waste time on fixing this.

[mel4tonin4]

I'd like to gradually experiment with Compose in a JavaFx application which is the desktop version and the control panel of the supporting service of a mobile application, and this is a showstopper for me, too.
Please, do not ignore this issue.

[olonho]

@dector could you please check if issue has gone with the build "0.2.0-build123"?

[dector]

@olonho 0.2.0-build123 fixes this issue for my sample.