Would it be possible to make compose support linux (and maybe other targets) natively, since it already supports darwin? Or is there still a lot of work to do?

Hello, I'm trying to align a composable with a part of another and i really don't know how tohandle it. In the below image, i would like the playArrow iconButton to knows the placement of the column header and align with it (don't look at the text, it should be centerrered too)

Does anyone know of a good tutorial for Decompose? I’m at a loss since the code in the documentation seems to contain errors…

Hi! I'm trying to write some code that works with a stylus, but I'm having a hard time. A lot of the stuff I've encountered uses

Modifier#pointerInteropFilter

, but that method doesn't exist, which means I don't know how to get access to

MotionEvent

. Any and all help will be greatly appreciated!

Does anyone know how to combine static content with a

LazyVerticalGrid

? I’d like the “Hello darkness my old friend, I’ve come to talk with you again” message to scroll as well when the user scrolls thru photo’s

There wouldn’t happen to be a way to move the scrollbar to the right side of the element we’re scrolling is there? 😄

Hello , does compose desktop support native image(graalvm)？

Is it necessary to remember stuff inside the

application

block? For example

application {
    val settingsStorage = remember {
        OfflineSettingsStorage()
    }
    Window(
        title = "ZenBreak settings"
    ) {
        MainView(// Params...)
    }

When does the application block recompose? And is it safe if we use remember then?

I need to have a special kind of window, something like this app does: A window that fills the whole screen and that opens on top of current applications, even if they are fullscreen (the app in the screenshot is made in electron, here is how it does it https://github.com/tom-james-watson/breaktimer-app/blob/master/app/main/lib/windows.ts#L80) I have two main issues: • getting the size of the screen in

Dp

• opening the window on top of the current application Seems like on electron there is this option which is what I need:

breakWindow.setVisibleOnAllWorkspaces(true, { visibleOnFullScreen: true });
// Or maybe it's this one
breakWindow.moveTop();

Is this possible with swing and compose? Otherwise if it’s not possible • how can I request focus on the window so that the user gets moved to it?

I've got a user encountering a memory leak in production on windows. We can't reproduce it locally. What steps would you take to diagnose an issue like this? I've never really delved into hprofs or anything like that. Any time I've ever tried looking into memory issues and discovering where they originate, I've found it very challenging to find the source from tooling, however we have the advantage of using the JVM, so there are bound to be tools for this, right?

Is there any example on how to implement a

floatUniform

effect for a runtime shader in desktop?

I am developing desktop app by using the compose, any one have idea how to do localization for desktop? Just like have in string.xml file in Android. Please share any demo if have it. thank you in advance!

I have added the "onPointerEvent" modifier on the common code, but now it doesn't compile for Android. I guess it doesn't exist on Android. What is the best strategy to add platform-specific modifiers?

I have a simple CountDown indicator which is made like so:

@Composable
fun BreakPopup(
    duration: ZbTimeData,
    onTimeFinished: () -> Unit,
) {
    var progress by remember {
        mutableStateOf(1F)
    }
    val animatedProgress by animateFloatAsState(
        targetValue = progress,
        animationSpec = tween(
            durationMillis = duration.millis.toInt(),
            easing = LinearEasing
        ),
        finishedListener = {
            onTimeFinished()
        }
    )

    LaunchedEffect(Unit) {
        progress = 0F
    }

    // Etc...
    RoundedCornersCircularProgressIndicator(
        progress = animatedProgress,
        color = textColor,
        strokeWidth = 8.dp,
        modifier = Modifier
            .fillMaxSize()
            .padding(8.dp)
    )

And I show it in a simple window

Window(
    visible = isPopupWindowVisible
) {
    BreakPopup(message = settings.value.breakMessage,
        duration = settings.value.breakDuration,
        onTimeFinished = {
            isPopupWindowVisible = false
        },
    )
}

I’m encountering a weird issue where the composable doesn’t seem to get disposed when the window is not visible anymore, because the first time it works correctly, while from the second time and on the progress is already at

0F

, and it seems like it’s holding the same composable with the old values instead of recreating it when the window is not visible anymore

Hi all. Not sure if this is the best channel to ask this question, but do we have any rough timeline on when we can expect

compose-multiplatform@1.5.0

to be promoted to stable and released? Wanting to pull this in for my prod project but slow maven instance from jetbrains dev space (

"maven(<https://maven.pkg.jetbrains.space/public/p/compose/dev>)"

) is making me reluctant to jump on right away.

Is there an easy way to tell what composables work cross platform? Is there a list somewhere? What about material, etc?

Is there a way to override the default undo/redo in compose desktop textfield

HI, how we can check if VerticalScrollbar is visible or not if we want to use some custom style there ? SO that depending on visibility, we can hide show our custom design

Hello! I'm currently really struggling with how to properly manage state in Compose. For example, I currently have this code below:

data class PointPath(
    val pathPoints: List<PathPoint>,
) {
    fun smoothPath(): PointPath { ... }
}

I made the data class immutable since recompositing isn't triggered when the list is updated and made it so anything that modifies it returns a copy (ex.

smoothPath

). However, this feels very cumbersome since I need to manually update the state with the returned copy. Is there a more effective way to do this, especially when it comes to handling the state when object properties change?

How frequently is the multiplatform fork synced with the core compose sources? Does that only happen close to the stable release? If so, is there no concern that most / all dev builds do not get good coverage since they don’t have the changes happening in the core development? For example,

1.5.0-dev1084

is still on the old implementation of modifiers

Is there a releases page for the Compose Multiplatform Compiler? It would be nice to use Renovate/Dependabot to keep it up to date. Also, is it expected to trail Jetpack Compose Compiler releases by 1-3 months, or is the compiler on a different release schedule (like the Jetpack Compose Compiler)?

I am creating a 2d canvas and want to integrate several “views”, and I need to have a compatability with JavaFX. However it seems that jfx panels do not respect composables’ parameters, such as zoom or zIndex. Offset and size are respected though. In the example below I have a WebView as example but I assume other JPanels will behave the same

I have just upgraded my Compose multiplatform project (desktop & android) to Kotlin 1.9.0 and Compose 1.5.0-dev1114. This works without problems when I run from the IDE or when I execute the gradle task ‘runDistributable’. But when I try to execute ‘runReleaseDistributable’ the build part works fine too but the program crashes immediately with:

Exception in thread "main" java.lang.VerifyError: Instruction type does not match stack map
Exception Details:
  Location:
    androidx/compose/animation/core/AnimationSpecKt.estimateAnimationDurationMillis(FFFFF)J @604: dstore
  Reason:
    Type top (current frame, locals[68]) is not assignable to double (stack map, locals[68])

Has anybody else observed a similar behaviour? Issue: https://github.com/JetBrains/compose-multiplatform/issues/3387

I'm trying to add text with a link to an

AnnotatedString

, using

withAnnotation(UrlAnnotation(myUrl)) { append("my text") }

, and with

withAnnotation("url", myUrl) {...}

, but neither are actually making the text clickable. Am I misunderstanding how the API works?

Are there any plans to make SplitPane multiplatform? For now it works only on desktop.

What's the best way to architect if I have some of my state that's dynamically refreshed from the db and the presenter class (sql delight / flows), and some of my state that's not externally refreshed (e.g. view scrolling state / mutablestate variables). I feel it's kinda conflicting because I would like to just recreate a immutable data holder with data from the db every time, but maintain the state class with e.g. scrolling state over time. I could use separate classes and a separate argument in the Composable, but sometimes these datas have an interplay, e.g. zooming around the data, I need to access the data sourced from the db for that. In that case, should I just keep everything in one class? Basically I just feel like the state flow from the db makes things awkward, because of having to call collectAsState() in the composable I'm using molecule in the presenter class by the way

I am trying to replace the

material

dependency with

material3

, but it looks like some components are not yet available in

commonMain

, an example is

ModalBottomSheet

Is there a plan to implement this or is it expected to not be implemented until

AlertDialog

is fully supported in common?

Has anybody else realised that you cannot create release builds with the latest version 3.4.0 of Okio once again due to problems with ProGuard. See: https://github.com/square/okio/issues/1298 ? Sadly, in this case it does not help to just switch off the optimisations. Does anybody have an idea how to circumvent this problem by something else than just not using 3.4.0 or disabling ProGuard completely or building Okio myself with a real JDK 17? I guess I am not the only one who is using Okio 😉.

It’s happening…

If using Spring interop is it generally preferable, given a choice, to use

ComposePanel

within Swing based UI or

SwingPanel

instead Compose based UI? (from a performance perspective)