Trying to get rid of the spaces where these buttons meet, I made the borderstroke match the background, and made the button rectangleShape, but there is still a little bleedline or some shadow areas in between buttons where they don't perfectly meet, is it possible to remove that?

Sorry to spam the channel but having trouble getting my stones on top of the corner now that I am no longer using Material Button. Even if I put the grid in a drawBehind { } scope the stones keep being drawn underneath the grid lines (or all the grid lines are invisible and only the stones can be seen). I tried playing with elevation and zIndex, but the lines and circles are still technically in modifier/canvas of the same Box scope, so i can't seem to get it behind as I would like.

@Composable
private fun tileButton(
    isVisible: MutableState<Boolean> = mutableStateOf(false),
    turn: MutableState<Int> = mutableStateOf(0)
) = Box(
    modifier = Modifier.background(accentAmber).size(60.dp).padding(0.dp).border(0.dp, accentAmber)
        .clickable(onClick = {
            isVisible.value = true
            turn.value += 1
        }).drawBehind {
            drawVerticalLine()
            drawHorizontalLine()
        }.drawWithContent {
            drawCorrectColorCircle(isVisible, turn)
        }) {
}

I try to migrate to v1.0.0-alpha3 singleWindowApplication() I have a "Image" that I created from a local "icon.png" that I used for the "icon" field. Now I need to provide a "Painter", but painterResource() can't be used as parameter that is a Composable. Looking at https://github.com/JetBrains/compose-jb/tree/master/tutorials/Image_And_Icons_Manipulations I don't see how I can now set my window icon... Can you please show me an example how to do that?

Hi. I see if I add a java file and try to build an app with compose-jb I get this dreadful error in

compileJava

task: https://pastebin.com/ghZLKS21 (Could not resolve all task dependencies for configuration) Is it correct that I can’t build a compose desktop app with java source code? I tried to bring Dagger in my compose-jb target and as it generated java files I got such an error… The changes for ToDo sample app to reproduce the behavior: https://github.com/soniccat/compose-jb/commit/df0dc8a88e8cbb4bb0abd8e88e22f20ac8d676ea Also I had the same problem here for some reasons: https://kotlinlang.slack.com/archives/C01D6HTPATV/p1628078176106900

Is anyone able to use Compose Preview for Android with Arctic Fox (Full Release) and the latest Multiplatform Compose Artifact (

1.0.0-alpha3

)? It's failing with this in the Preview window:

The following classes could not be found:
- androidx.compose.ui.tooling.preview.ComposeViewAdapter

...searching this error shows it was notoriously common throughout the Arctic Fox Beta's, but supposedly fixed for release. Does the Multiplatform Compose artifact need to be updated? Desktop Preview's working, but Android doesn't.

Also I was mildly disappointed to see that the Desktop Preview and Android Preview are: • Still in separate panels - is it not feasible to integrate Desktop preview with the Android Code / Split / Design system? • Cannot work from

common

source set i.e. define a

@Preview

from within some

materialCommon

(Desktop + Android) source set. When we develop a Multiplatform Project for Desktop + Mobile this is (very happily) where we can define most of our Compose components, so not being able to define

@Preview

here as well, sadly makes the Preview feature useless in this scenario. I played with different `expect`/`actual` definitions for the

Preview

annotation, but couldn't make anything that improved the experience.

✅ RESOLVED: I am wondering why there’s no default implementation for

onCloseRequest

of the new

Window

API? Why

onCloseRequest: () -> Unit

and why not

onCloseRequest: () -> Unit = { exitProcess(0) }

? 🤔

✅ RESOVED: `Window`*’*s

icon

property not working 🧵

Shouldn't the

ContextMenuDataProvider

work on every Composable and show menu (with custom entries) on right click? Doesn't work for me on Text, but works fine (with defaults) on TextField. Tested with alpha 2 and alpha3. Code in 🧵

I see that the multiplatform template was updated to include this

named("commonMain") {
            dependencies {
                api(compose.runtime)
                api(compose.foundation)
                api(compose.material)
                // Needed only for preview.
                implementation(compose.preview)
            }
        }

Does this mean that preview is available in common code?

Compose doesn't work on 32-bits windows ?

Hi! I’m trying to include the Coil-Library in my test project: I’ve added the following line to my build script:

implementation("io.coil-kt:coil:1.3.2")

But then I build i I get the following error message(s):

Could not resolve all files for configuration ‘:compileClasspath’.

> Could not resolve io.coil-kt:coil:1.3.2. Required by: project : > No matching variant of io.coil-kt:coil:1.3.2 was found. The consumer was configured to find an API of a library compatible with Java 15, Any ideas how to solve this?

[Solved✅] Hi, I'm trying to create a multiplatform project with android and jvm targets. But I got

java.lang.OutOfMemoryError: Java heap space

on

:android:mergeExtDexDebug

task when building android mudule. My compose version is "1.0.0-alpha3". Here is my project structure: common module ---- service (written as

expect class

) ---- compose ui, viewmodel (dependens on service) android module ----

actual

service ---- Activity that boots compose ui. jvm module ----

actual

service (exactly the same as android) ---- Main function that boots compose ui. If I only build jvm module, all work fine. I try to move the code from common module to android module, and that works fine too. My codes were shared to my github repository, as a branch (https://github.com/Konyaco/CollinsDictionary/tree/multiplatform). And I wonder that is there a best way to reuse code between JVM and Android targets? The apis are same in most occasions.

:compose: Is there any plan to have Compose Desktop

@Preview

support 'Interactive mode' like Android? One of the very best things about Preview in Android is the ability to run Views with real ViewModels behind them; just with mocked services/data plugged in.

Hello, I have a question concerning the new

mouseClickable

on the Modifier. Is it possible, to register it multiple times? It currently consumes the event and just the last "registration" takes effect. I tried to create some convenient extensions, but just the last of it seems to be called:

@Composable
fun Modifier.onLeftClickOnly(action: () -> Unit) = mouseClickable {
    println("left")
    if (buttons.isPrimaryPressed && !buttons.isSecondaryPressed && !buttons.isTertiaryPressed) {
        action()
    }
}

@Composable
fun Modifier.onMiddleClickOnly(action: () -> Unit) = mouseClickable {
    if (!buttons.isPrimaryPressed && !buttons.isSecondaryPressed && buttons.isTertiaryPressed) {
        action()
    }
}

@Composable
fun Modifier.onRightClickOnly(action: () -> Unit) = mouseClickable {
    println("right")
    if (!buttons.isPrimaryPressed && buttons.isSecondaryPressed && !buttons.isTertiaryPressed) {
        action()
    }
}

Does Compose Desktop has paging composer like in https://developer.android.com/jetpack/androidx/releases/paging ?

My team officially merged in Compose Multiplatform support! So excited to start making all of our composables usable between desktop and android! 😛arty-parrot: Edit: My PR to merge it in was there for about 3 months. Thank you @Igor Demin for all the information I needed to convince my team to merge!

One thing that seems a little bit off is that our Desktop sample app compiles and runs just fine but has red lines all over. We're using Android Studio bumblebee canary 6. Using JDK14 as my JAVA_HOME. Using Android Gradle Plugin 7.1.0-alpha06 as well. Edit: Used Android Studio Arctic fox and downgraded to AGP 7.0.0 and I get the same issue. /shruggie

Is there a known issue where resizing windows is just plain broken?

Hello, is there a way to get a reference to the main thread (

java.lang.Thread

) of a Compose for Desktop app? My use case is checking whether some code is running on the main thread or not, to disallow running some blocking code where it could affect the UI.

Hi, trying the first example at https://github.com/JetBrains/compose-jb/tree/master/tutorials/Image_And_Icons_Manipulations

painterResource

can't be found (on Desktop). Is there an alternative?

Ring UI is beautiful which is used in ToolBox App. I think it is a good idea to provide the UI design in Compose Desktop.

Cannot render svg file correctly, but can android xml file. The xml was converted from svg by Android Studio. Is this a bug?

val WordNotFoundLRes = painterResource("wordnotfound_l.svg")

Image(
    painter = WordNotFoundLRes,
    contentDescription = "Word Not Found",
    colorFilter = null
)

How can I test the visibility of an (alert) dialog and its content with a Unit test? I'm using the new Dialog/Window API and wrote successfully some Unit tests with the test rule. When the dialog is displayed it doesn't work. The matchers (e.g.

onNodeWithText

) can't find the text and I assume it's because it's in a different window and the rule can't access it? Did look into the

DesktopComposeTestRule

and saw that it creates a window for the test and so on, but can't figure out a way to test the visibility of the dialog texts.

Just wondering if anyone had a few minutes to spare today to see if they can repro my issue here: https://github.com/JetBrains/compose-jb/issues/1038 All you need is the multiplatform template and the code I attached in the issue to repro (don't forget to invalidate and restart). I'm trying to figure out if this is a local env issue or if everyone can repro.

I'm having a hard time using desktop compose in Android Studio. AS can't seem to find many classes even though I have the libraries as dependencies

What are the chances that the compose team will support auto-update functionality? I’m trying to navigate creating an auto-updating app, but it seems that I’d have to abandon the benefit I’d get from compose doing the packing for me and packing everything myself, which obviously isn’t desirable.

Hi, I was recently investigating whether compose desktop meets the company’s needs, and one of the goals was to support GIF and animation performance. However, I found that compose desktop does not provide GIF support, and I found two code snippets in the related issue[0], but the performance difference between them is huge. The first one [1], written by @Dominaezzz, is very easy to understand and intuitive, but the CPU usage hovers around 100%. The second one [2], written by @olonho, is a bit more complex, but has better performance, with a CPU usage of around 25%. But I would say that either solution is not really acceptable. And I would like to know how we should write high performance animations? I actually tried to use java swing ImageIcon and it hardly uses any CPU usage. I believe compose desktop should be able to do the same, but how should I do it? [0]: https://github.com/JetBrains/compose-jb/issues/153 [1]: https://github.com/JetBrains/compose-jb/issues/153#issuecomment-864608382 [2]: https://github.com/JetBrains/compose-jb/issues/153#issuecomment-822439430

Has anyone seen this error? (I am not using Android Compose):

You are using an outdated version of Compose Runtime that is not compatible with the version of the Compose Compiler plugin you have installed. The compose compiler plugin you are using (version 1.1.0-alpha01) expects a minimum runtime version of 1.1.0-alpha01