Noob question about multi modules and compose android and desktop. I've worked with compose on android and desktop very little and I've never worked with a multi module android app. In this case though... I have a fairly simple existing app that I already added compose to, but my plans are to add a new module to my android app that houses compose called

composables-common

I already created this module in Android Studio as a new android library module. Now I want to create a new module in the same project that is a compose desktop module and have it depend on

composables-common

Two questions: 1. Is making my composables-common module supposed to be a

com.android.library

module? 2. Does anyone see any issue with my "proposed" setup? Existing android app module. Create new composables-common android library module. Set this composables-common as a dependency in my existing app module. Create new compose desktop app plain ol java module. Depend on composables-common dependency in the desktop module. Working on Android? Open the project in AS and choose android app module to launch. Working on desktop? Open the project in IJ and choose desktop app module to launch. I have seen the sample projects showing desktop and android app in a single repo, but I guess I'm more stuck on how to do it for an already existing project. Thank you!

Hello! In ui-desktop dependency there is composable AppWindow. It exists only for jvm target. Is there any plans to make it common? (For native linux, windows, mac os)

I have the following piece of logic:

@Composable
fun EditPartUI(part: Part, onDismiss: () -> Unit) { /* */ }

@Composable
fun PartXX() { 
    var pendingPartCreate by remember { mutableStateOf<Part?>(null) }
    
    if(pendingPartCreate == null) {
        ScrollableTab(
            onFabAction = { pendingPartCreate = Part() }) {
            // ....
        }
    } else {
        EditPartUI(pendingPartCreate!!, onDismiss = { pendingPartCreate = null} )
    }
}

The

else

branch does not compile unless I use

pendingPartCreate!!

(smart cast does not work). So is the compiler not smart enough to detect the fact that it cannot change? Or is the compiler rightfully wants to prevent me from shooting myself in the foot?

Is there any Documentation for testing compose on Desktop and what dependencies I need to implement into my grade project?

Hi, Is there any version Compose version built with

1.5.0-M2

? If not, do you plan to or should we be waiting for

1.5.0

?

Is there any known animation issue with

0.4.0-build178

?

animateFloatAsState

doesn't seem to work anymore. 🤔 🧵

Is there any example of writing UI tests with compose desktop?

I am wondering why's everyone going after testing this week 😆

Hi, someone has tried to build the Msi package? I am trying but the command gives me an error on Windows

Hi, someone knows how can create a desktop launch (installed)? for every platfform

Hi, someone knows why (In windows) the app don't appear in the searchbox?

Can I change the background color of the window? 🧵

What are the most common ways to provide multi language support?

This has probably been asked before, but is there a way to know what Compose version from Google is being used in Compose Desktop builds? Like is

beta01

in

0.3.0

?

I would appreciate OS-independent APIs to get system colors, like for controls, backgrounds, text, etc. And it should properly respond to system theme change, like dark/light or even custom. Is there something like this on the roadmap?

If I try to have a single module common-composables that are shared for desktop and android... am I "held back" by the version number that desktop supports? I know desktop is slightly behind and just curious if that basically means I'm always going to be a ~week+ behind on compose releases.

https://github.com/JetBrains/compose-jb/releases lists all the releases now

Is compose-desktop feasible for desktop-only apps? Or am always going to be constrained by its mobile-centric roots? I'm needing tooltips, file pickers, font pickers, that sort of thing...

This version (1.0.0-alpha13) of the Compose Compiler requires Kotlin version 1.4.31 but you appear to be using Kotlin version 1.4.32

so we need to downgrade the kotlin version ? 🙄

What components should I be using to create something like a font selector dialog? E.g. I have a Box with a LazyColumn and a VerticalScrollBar. Inside the LazyColumn is a Text item - but how do I make the Text item 'selectable'? Should this be a button instead? Or?

I am a new learner, learning Jetpack Compose. I came across Compose-Desktop during the process. So I tried searching web about the difference between Qt/TornadoFX/Compose-Desktop. Can Compose-Desktop be used where we use Qt? Moreover TornadoFX is itself in Kotlin, so which one is better to focus on for a novice in UI programming?

I did a proof of concept for a LiveCanvas component where you can change code inside of the Canvas during runtime and it will compile the changes as Kotlinscript instantly. https://gitlab.com/compose1/livecanvas-poc

So I'm almost 100% certain this ain't the correct place to ask. but I'm not really sure where else to ask, so here it goes. I'm using Jetpack compose for desktop and I'm using

decompose

for my navigation and to decouple my logic from my UI, however I'm little bit stumpped on this one problem, two pages I have need to share same state and I'm struggling to figure out how to pass it down to both of them, the closest I got was to put it in my NavComponent class and try to pass it down through the child

render

functions, I reckon if i tinckered abit more, I could maybe of got it too work, however this was getting really ugly and hard to maintain which makes me feel like I'm doing it wrong, so I reverted the changes back and I'm now asking for any examples or further advice on how to aproach something like this with

decompose

Is there a build compatible with 1.5-M2? `e: This version (1.0.0-alpha13) of the Compose Compiler requires Kotlin version 1.4.31 but you appear to be using Kotlin version 1.5.0-M2 which is not known to be compatible. Please fix your configuration (or

suppressKotlinVersionCompatibilityCheck

but don't say I didn't warn you!).`

Building a desktop app, and using

Modifier.combinedClickable().indication()

on a

Box

, and having a hard time figuring out how to just set the indication to null. As I understand it, I should just be able to set

indication = null

, but when I do

.indication(indication = null)

it complains about no value passed for

interactionSource

. Not really sure what I should pass there. There was this workaround I found from a few weeks ago (

interactionSource = remember { MutableInteractionSource() }, indication = null

) but that doesn't seem to have any effect, the indication is still there.

Have an extension of the question @v79 asked the other day

Is compose-desktop feasible for desktop-only apps? Or am always going to be constrained by its mobile-centric roots? I'm needing tooltips, file pickers, font pickers, that sort of thing...

If someone is interested in building primarily a desktop app (maybe a mobile app port someday), how do Flutter and Compose-desktop compare for that purpose? (I know there are probably many Flutter vs Compose questions but, sorry, it's very confusing as an outside observer)

Haha! This was a little unexpected from a `BasicTextField`function!

Hello here 👋 I’m working on an open source project (https://github.com/GerardPaligot/discovering-movies) where I want to try compose on Android and Desktop. I had never tried Compose Desktop before but I’m surprised to see that Compose Desktop have their own Compose librairies. There is no way to share components between platforms?

I have no idea how it works on Android, so posting here, but it could be generic problem. In modern OSes when you push the button (but don’t release the mouse!), move cursors away from button it gets depressed, and if you release it, no click is registered. All fine here. But, if you don’t release mouse after moving away, and move cursor back into button area, it gets pressed back and if you release the mouse the click is registered. This is not working in Compose (desktop).