I have a question with using SQLDelight in a Compose desktop app. Right now, my main function instantiates ApplicationState -> WindowState -> etc. Where do you usually instantiate the Database object and add initial content to it? And do you do that in a Repository singleton with Kotlin flows? Just wondering if there's some sample app that people can share. Thanks!

Hi everyone, I'm working on a Compose Desktop app that includes Retrofit and the need for XML {de,}serialization. I started down the road using simple-xml, but found out later that Retrofit's Simple XML converter is deprecated in favor of their JAXB converter. The interesting thing is that there appears to be two: jaxb and jaxb3. The former seems to be based on

javax.xml.bind

(which I think is the Oracle JAXB implementation), while the latter is based on the

Jakarta

JAXB implementation from The Eclipse Project. Are there any license or other issues with using the

jaxb

converter (and, by extension,

javax.xml.bind

)? I'd prefer the

Jakarta

-based converter, but I can't find an artifact for it on Maven. I suppose a more general question is "which is the recommended XML converter to use with Retrofit?"

I'm seeing a strange issue. If I load JCEF before my compose window is created, my compose window can't be resized. It basically freezes. If I load JCEF after compose window is displaying, it seems to work. I'm curious if anyone has seen anything like this before. I created an issue here - https://github.com/JetBrains/compose-multiplatform/issues/2939

Hey there; I may have found a regression in the newest Compose but wanted to confirm that I'm onto something first. This concerns compose going from 1.4.0-alpha977 to 1.4.0-alpha1000. I noticed the following issue: I have a desktop+android app, in

commonMain

I use

implementation(compose.uiTooling)

. In

1.4.0-alpha1000

, I see the following dependency tree for my desktop variant:

+--- org.jetbrains.compose.ui:ui-tooling:1.4.0-alpha01-dev1000

|    \--- org.jetbrains.compose.ui:ui-tooling-desktop:1.4.0-alpha01-dev1000

|         +--- org.jetbrains.compose.ui:ui-tooling-data:1.4.0-alpha01-dev1000

|         |    \--- org.jetbrains.compose.ui:ui-tooling-data-desktop:1.4.0-alpha01-dev1000

|         |         +--- androidx.compose.runtime:runtime:1.2.1

|         |         |    \--- org.jetbrains.kotlinx:kotlinx-coroutines-android:1.6.1 -> 1.6.4

Note the coroutines-android at the end. It seems this causes Android's

MainDispatcherFactory

to be present in the source, which takes precendence over Swings

MainDispatcherFactory

. As a result, my desktop app tries to load Androids Main Dispatcher and crashes. In

1.4.0-alpha977

this dependency doesn't exist:

+--- org.jetbrains.compose.ui:ui-tooling:1.4.0-alpha01-dev977

|    \--- org.jetbrains.compose.ui:ui-tooling-desktop:1.4.0-alpha01-dev977

|         +--- org.jetbrains.compose.ui:ui-tooling-data:1.4.0-alpha01-dev977

|         |    \--- org.jetbrains.compose.ui:ui-tooling-data-desktop:1.4.0-alpha01-dev977

|         |         +--- org.jetbrains.compose.runtime:runtime:1.4.0-alpha01-dev977 (*)

Now, given that

uiTooling

has an explicit

desktop

variant it should probably be fine to use it in non-Android environments. So I'm guessing this has been a bug introduced by the recent merge of Google's Compose 1.4.0 where uiTooling doesn't depend on the correct runtime anymore?

There’s a big issue with builds 991 and 1000 reported at https://github.com/JetBrains/compose-multiplatform/issues/2946. Anything that involves updating a composition local hangs the whole app indefinitely. 985 is the last build that works.

I have a slider that has a ‘steps’ value. It responds correctly to the mouse, moving to the step and calling the onValueChangeFinished callback. The slider also responds to the keyboard so when I give it focus I can use left and right arrow to move the slider, that also works but it doesn’t call onValueChangeFinished (onValueChange is called). Is this expected? Compose version is 1.3.1 Thanks

With the latest versions of Compose (desktop) I observe a very strange behaviour. After launching the application a whole view of my application is simply not rendered anymore although there is no error message or anything. Normally the screen looks like in screen1.png (only a fraction of the full screen is shown here) but now it looks like in screen2.png. As you can see, the whole part with the search field and the gray area where a tree view appears once data is loaded, is simply gone. If, however, I switch to another screen and then come back to this one, it is rendered normally. This change in behaviour happened between 1.4.0-alpha01-dev984 and 1.4.0-alpha01-dev985 and is still apparent in later versions. Does anybody have a clue what might have triggered this and what might be a possible workaround? The app has been working nicely for weeks now and this is really throwing me back.

Is build 999 “after” 1000? Does it have fixes for the double window recomposition?

Is it possible to change the ‘display name’ of the application. When I Cmd+Tab on the Mac the name of the app shows a ‘MainKt’, can I change this to something meaningful?

Sort of related to the above, I’m now trying to create and run the app, I’ve tried ‘packageReleaseDistributionForCurrentOS’ and ‘packageReleasePkg’ but when I install and run the app I get java.lang.UnsatisfiedLinkError: Can’t load library: /Applications/drawgrid.app/Contents/app/libskiko-macos-arm64.dylib This answer on SO (https://stackoverflow.com/questions/70150052/org-jetbrains-skiko-libraryloadexception-cannot-find-libskiko-macos-arm64-dylib) says to change the compose.desktop reference or to update to the latest plugins (the answer is from over a year ago) I get the same behaviour if I just create and build an empty ‘demo’ project

Question related to using SQL db (lmk if there is a better channel): I added a SQLite database to my app. What's the best pattern to recover data e.g. if the computer has a power loss. In-memory database would be lost right? Should I create a working database in a temporary folder and then load/save that database to the user's document folder when user wants to save? thanks

I think I have stumbled again over a regression in Compose. Going from 1.4.0-alpha01-dev984 to 985 my AlertDialogs changed from looking like this to

Hello! I've noticed that having multiline text field and scrolling text area without focus and then click to some line, text area is scrolling back to first line, while cursor is pointer to place where click happened. When text field already focused scroll position not changes on click as expected. Is it a bug or expected behaviour? If second how can it be specified for not scrolling on focus?

A newbie question. Is there a recommended way to store user preferences, preferably one that works across platform or if not some guidance for each platform (Desktop, Android, iOS)? Thanks

Hello 👋 I'm trying to package and distribute a dmg for my compose desktop app. I followed the tutorial in the readme and even what's described in this issue. The app is badly crashing at startup with a sigtrap. It's even crashing if I run the app with

runDistributable

(

finished with non-zero exit value 133

). I noticed that the crash will stop if I comment out the

signing

block in my gradle configuration. I've tried every jdk from 15 to 19 (zulu). I'm using Kotlin 1.8.10, compose 1.3.1. Anybody has any clue about what I'm missing? Stacktrace and gradle config is in the thread 🧵

When I show a certain screen in my application I notice that the CPU usage goes higher than normal and goes back to normal as soon as I leave that screen. I assume there is some hidden recomposition loop somewhere. What are my best options to debug this? Any ideas?

Is there an explainer somewhere for how releases work in the compose-multiplatform repo? I get frequent notifications of new releases, but almost none of them have any release notes associated with them

I have a question that's not so much about Compose as about desktop applications... how do you know where to store files for the user? Is there any standard for that, or does everyone just have to reinvent that particular wheel for their own application?

Apologies if this question is obvious, I've spent a while searching (even asking chatgpt) but how do I get a working vertical scrollbar on a multi-line text field. For some reason one doesn't appear by default. I tried using

VerticalScrollbar

and syncing them via a

scrollState

but it doesn't seem to work properly.

Is it possible to use a newer version of material3 or is it bound to

compose-multiplatform-core

release cycle? For the upgrade from material2 to material3 I need

ModalBottomSheetLayout

and it seems to be available in googles compose material3 version

1.1.0-beta01

.

Is there an API to create a

FontFamily

from a string e.g. "SF Mono"? I only see the resource based Font class.

Hi all 👋. I’m starting a new project in KMM, any tips are welcome !! BTW any one knows if WebView/BrowserView will be released as standard component for Desktop soon ? (edited)

Hello, I developed a tool using Composite Desktop. if execute ‘run’ commend,the tool is fine.but when i execute ‘runDistributable’, There will be an error. Has anyone knows what happened?

Exception in thread "DefaultDispatcher-worker-2" java.lang.IllegalArgumentException: Unable to create converter for class net.ModuleInfoResp0
    for method RetrofitService.getModuleInfo0
	at retrofit2.Utils.methodError(Utils.java:54)
	at retrofit2.HttpServiceMethod.createResponseConverter(HttpServiceMethod.java:126)
	at retrofit2.HttpServiceMethod.parseAnnotations(HttpServiceMethod.java:85)
	at retrofit2.ServiceMethod.parseAnnotations(ServiceMethod.java:39)
	at retrofit2.Retrofit.loadServiceMethod(Retrofit.java:202)
	at retrofit2.Retrofit$1.invoke(Retrofit.java:160)
	at com.sun.proxy.$Proxy0.getModuleInfo0(Unknown Source)
	at net.RetrofitService$DefaultImpls.getModuleInfo0$default(RetrofitService.kt:17)
	at ui.Module0Kt$Module0$2$1.invokeSuspend(Module0.kt:23)
	at kotlin.coroutines.jvm.internal.BaseContinuationImpl.resumeWith(ContinuationImpl.kt:33)
	at kotlinx.coroutines.DispatchedTask.run(DispatchedTask.kt:106)
	at kotlinx.coroutines.internal.LimitedDispatcher.run(LimitedDispatcher.kt:42)
	at kotlinx.coroutines.scheduling.TaskImpl.run(Tasks.kt:95)
	at kotlinx.coroutines.scheduling.CoroutineScheduler.runSafely(CoroutineScheduler.kt:570)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.executeTask(CoroutineScheduler.kt:750)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.runWorker(CoroutineScheduler.kt:677)
	at kotlinx.coroutines.scheduling.CoroutineScheduler$Worker.run(CoroutineScheduler.kt:664)
	Suppressed: kotlinx.coroutines.DiagnosticCoroutineContextException: [androidx.compose.ui.awt.ComposeLayer$coroutineExceptionHandler$1@23bd828d, androidx.compose.runtime.BroadcastFrameClock@772580d1, StandaloneCoroutine{Cancelling}@3aa10bfa, <http://Dispatchers.IO]|Dispatchers.IO]>
Caused by: java.lang.IllegalArgumentException: cannot construct instances of net.ModuleInfoResp0
	at com.squareup.moshi.ClassFactory.get(ClassFactory.java:133)
	at com.squareup.moshi.ClassJsonAdapter$1.create(ClassJsonAdapter.java:79)
	at com.squareup.moshi.Moshi.adapter(Moshi.java:137)
	at com.squareup.moshi.Moshi.adapter(Moshi.java:97)
	at retrofit2.converter.moshi.MoshiConverterFactory.responseBodyConverter(MoshiConverterFactory.java:89)
	at retrofit2.Retrofit.nextResponseBodyConverter(Retrofit.java:362)
	at retrofit2.Retrofit.responseBodyConverter(Retrofit.java:345)
	at retrofit2.HttpServiceMethod.createResponseConverter(HttpServiceMethod.java:124)
	... 15 more

Is it possible to enable hardware acceleration and use GPU for a compose desktop project ?, when I use the project the GPU usage is 0% in the activity monitor.

I just started to build and package my Compose desktop project on Windows for the first time. The build failed because of some missing wix tools. I noticed in the logs that downloading these tools was skipped for some reason. So what is the current state of the system? Am I supposed to manually download and install these things or should they be installed automatically and something is going wrong here?

I set up a compose-multiplatform project in IntelliJ using its built-in template, and there's something wrong with the Gradle project it produces, or perhaps IntelliJ's integration: The source and test directories aren't marked as source and test, so I don't get Kotlin highlighting, completion, etc. I can manually mark them, but any Gradle reload undoes it. Interestingly, the resource directories are properly marked! Any tips?

When using

clickable

modifier, it's applied on mouse up (pointer release) instead of mouse down, which creates a noticeable delay in the UI. (User expectaion is for the action to happen on press, not during recoil) Is that a known issue? I don't find anything about it in the bug tracker.

I'm wondering, do I need to use

focusable

or some other focus modifier for

onKeyEvent

modifier to be called on a composable? I'm trying to implement keyboard navigation in a

LazyVerticalGrid

with a selected cell, but

onKeyEvent

isn't being called. I've used the

Window

onKeyEvent so far but I have several composables in the window that need keyboard navigation and so I want to have precedence order based on who is in focus :)

We published Compose Multiplatform

1.4.0-rc03

with Kotlin 1.8.20 support. 1.4.0-rc03 will be 1.4.0 if there are no critical issues and regressions. Any feedback is appreciated 👍.

Hey there. In the compose image-viewer example there is a rules.pro proguard file but I don't see it referenced anywhere. Is "rules.pro" hardcoded as a default? I did find a gradle file from a test project that explicitly adds the file, making me think that it's not used by default.