Afaik compose is compatible with kotlin 1.5.10. What if a library is compiled against 1.5.20. Will that cause an incompatibility?

I have a TextField with

singleLine = true

and

maxLines = 1

, but in the emulator I can still press keys like ENTER to create newlines, can I somehow prevent that? Or should I just filter stuff like

\n

in the valuechange?

Is it possible to move Floating Action Button above keyboard when using Scaffold?

Hey, i'm trying to do something really simple but having some problems. i have a Row(text,icon) and the text can be super long so i made it

maxLines = 1

, and

overflow = TextOverflow.Ellipsis

so it can be like. "Lorem ipsum ..." ⬆️ but if i change the

overflow

to

Ellipsis

the text takes the whole row and it becomes -> "Lorem ipsum ..." without the icon i tried

inlineContent

also but that simple thing i couldn't achive anyone has idea?

How can I remove a Composable function entirely from UI Tree without losing state so that it does not visible, take spaces, consume events etc.? When I write like

if(someState) Content()

, the internal states may fly away. (such as value remembered by

remember {}

) Generally speaking, can I prevent emitting the nodes? (Maybe linking to another composition with wrapper Applier which conditionally delegates to parent applier..? - this would overkill)

Hi, did anyone tried compose on wear os? We are creating new app and we are not sure if we can already start with compose or use xml. It looks like there are some wear composable components but I wasn’t able to find BoxInsetLayout and other components specific to wear os. https://developer.android.com/jetpack/androidx/releases/wear-compose

SOLVED Hey 👋 Is it possible to fully clear the backstack using navigation component on compose? If I set the destination at the bottom of the stack with

inclusive = true

I’m getting the following exception:

androidx.navigation.NavGraph cannot be cast to androidx.navigation.compose.ComposeNavigator$Destination

The use case is a user that signs out, so I want to clear the whole backstack and then navigate to the login screen.

Hi 👋. Let's say I've have a complex object I want to persist even if the screen is rotated as state: should I use

ViewModel

or

remeberSaveable

? Which is best practice ?

Please I need help!!! I have problem with rotating and draging 😢 Like you see in the video When I insert image and draging it without rotate it (it's works fine ✅) But if I rotate the image and try to drag it It drags to the wrong sens ❌❌❌ Which is not what it suppose to drag !!! Any one have an idea how to fix it ?!

Is it fine to use two different kinds of

ViewModel

for the same

Composable

? This way I will have more granularity.

What's the gist for dealing with keyboard covering text inputs in a full compose app? If I have a screen that is not scrollable and it just contains a logo at the top and two text fields, but the keyboard covers the second text field, what paths forward do I have? 1. Is windowSoftInputMode still recommended in a full compose app? 2. Should I just make the entire page scrollable? Even though requirements say the page shouldn't scroll. 3. Can I only make the text inputs scrollable (wrap in a scrollable column) to make sure the keyboard doesn't cover. 4. Something else I missed? I initially was going to reach for windowSoftInputMode, but that always seemed fishy to me. Curious if there's a "proper" way forward with compose.

Do I have to do something special to close an

AlertDialog

pressing back key or clicking outside? I saw the

properties

parameter receives an

DialogProperties

object which has these properties (

dismissOnBackPress

and

dismissOnClickOutside

) set to true by default. But looks like it’s not working 😕

Is there list of icons to browse for jetpack compose?

I'm trying to use bottom nav and multiple back stacks. I can jump between tabs/stacks fine, but if I tap the icon for the current tab, and I'm not at the "root" of that tab, I go to blank screen. I have no clue why. Anyone seen this?

I have navigation problem. app has 3 screens 1st -> list of items 2nd -> item details 3rd -> gallery of item images I use compose navigation component version

2.4.0-alpha05

and am navigating from 1st to 2nd screen like this:

navController.navigate("$route/${id.value}")

and routes are defined like so:

@JvmInline
value class Routes(val route: String) {
    companion object {
        val Home = Routes("home")
        val ItemDetails = Routes("item_details/{id}")
        val ItemGallery = Routes("item_gallery")
    }
}

I access that

id

parameter inside

ViewModel

savedStateHandle.get<String>(ARG_ITEM_ID) // ARG_ITEM_ID = "id", same as route arg

when I go from 1st screen, list of items, to 2nd, details, it works fine BUT when I go from details to gallery and press system back button

ARG_ITEM_ID

is

null

. it works fine with navigation version

2.4.0-alpha04

How can I get the selected text from the

SelectionContainer

?

How do you usually handle initial null values for states? In the old way, I have a

Flow<T>

then I just observe it and wait for the initial value before I update the UI. Now, I’m trying to consume it and it always needs an initial value. I tried to do

.collectAsState(initial = null)

but then it makes it nullable and I have to perform null checking on every flow. Is there a better practice around this? I’d like to have

Flow<T>

rather than

Flow<T?>

. Thanks in advance!

I have a screen with a viewPager from accompanist. One thing that I'm having trouble with is syncing my viewModel.currentPage and rememberPagerState.currentPage, and remembered that one of the points of compose is single source of truth.

@Composable
fun SignUpScreen(
    viewModel: SignUpViewModel = hiltViewModel()
) {
    val pagerState = rememberPagerState(5)

In order to have a single source of truth, should I just move

val pagerState = rememberPagerState(5)

into my ViewModel?

I have a 3rd party sdk which provides a Fragment subclass I cannot change. Can I somehow wrap it in

AndroidView

and make all the fragment lifecycle work? (Since they don't provide a View)

I have a problem with what I thought would be a simple example I tried to write up for compose. If you are well versed in mutableStateListOf I could use your help. Code in thread.

Is there a way to have a special

BackHandler

that consumes back calls before the inner most composable? My use case is I have a

BottomSheetScaffold

at the root of my app (Theme>BottomSheet>Home>NavHost) and I want to close the sheet on back clicks. But BackHandler defined in BottomSheet doesn't get invoked until all back handlers deeper in the tree are used (in my case, NavHost consumes before BottomSheet, until the first destination is reached / nav stack cleared).

Is there anything special I need to do to prevent a non-state parameter to a composable function from messing with recomposition/skipping? For example:

@Composable
fun Parent(state: State, eventEmitter: EventEmitter<Event>)

eventEmitter

will always be the same instance for a given composition, and uses an identity based

equals

and

hashCode

. Is there anything else that I need to do? Note that I can't use

CompositionLocal

here because a lot of the events I need to emit occur in non `@Composable`lambdas (e.g.

onClick

).

How can I place an image on the screen with a concrete height (140.dp in this case) which then affects the width of the image, but I want to offset the image alllllll the way on the left. Right now I hardcoded it to -200.dp and it works great on my pixel5, but running it on the emulator, it doesn't get pushed off the screen entirely. Do I have to try to measure the width somehow after height is applied and set offset that way?

Box() {
    Image(
        modifier = Modifier.height(140.dp).offset(x = (-200).dp),
        painter = painterResource(id = com.myapp.myresources.R.drawable.catdog),
        contentDescription = null)
}

Hi, what is

dp

?

Is there in compose default android AlertDialog realization? I mean realization that include native dialog buttons style, title and text styles etc? Looks like that in compose AlertDialog i should customize style almost completely and it is perfect! But what if am i want only pass strings and actions into to see android native alert dialog?

So I have a question about the XML selector drawable is it the same use in Compose or there something I miss? basically I need to reflect an icon selection in a group of items

Hi Everyone, I want to create separate Compose Component Library and then use it in my Project, in some case i want to override the compose component from Product app. can anyone help me in this case

if I have a screen built entirely in compose, but a 3rd party library I want to use requires a

View

to be passed into it when using it to use as an anchor.. is there any way to do that? or is this type of interop impossible? it's important to note, the 3rd party library doesn't actually need to do anything with the

View

besides use it as an anchor point.. so if there was a way I could programmatically generate a view that could work I guess?

What happens to `AndroidView`s during orientation changes? Are they re-measured with swapped width/height? Drawn with rotated canvas? My activity has

android:configChanges="(everything)"

as suggested by compose team, so compose handles UI rotations. But I'm seeing issues with `SurfaceView`s in the compose hierarchy. Would love to have some insight about what's happening under the hood