Will future versions of compose be cross compatible with multiple kotlin versions?

Please, really please, fix this issue to stop getting notifications from +1 people 🙏 https://issuetracker.google.com/issues/160665122

hi. question regarding Navigation from Notification and keep backstack. My

MainActivity

is running and has the

ScreenA

and

ScreenB

in the backstack. If the user press the notification I would like to keep the

MainActivity

opened just adding the

ScreenC

to the backstack… Is there a way to do that?

I have a

NavHostController

to navigate using the

ComposeNavigator

API. I need access to it in certain

Compose

functions. Is using the

CompositionLocal

API suitable for efficiently pass it around? Seems like they need access to the same reference and I couldn't find a function that already does that... Something like this

val navController = rememberNavController()

    CompositionLocalProvider(LocalNavHostController provides navController) {
        NavHost(navController = navController, startDestination = navController.pathToMainScreen) {
            composable(navController.pathToMainScreen) { MainScreen() }
            composable(navController.pathToWifiScreen) { WiFiScreen() }
        }
    }

It seems Modifier.verticalScroll and LazyColumn contents are clickable even when scrolled off-screen. It's as if the contents are clipped only visually, but still on the screen (like View.INVISIBLE). Guessing that's a bug?

Hi! I'm using androidx.navigation:navigation-compose:2.4.0-beta02. Every time I make a NavController.navigate call, I see graphic memory allocations of roughly 30Mb to 100Mb that never get reclaimed by the GC. This leads to Out of memory errors within 5mn of normal use of my app. Am I doing something wrong? If the solution is not clear, what can I do to investigate the issue?

Hello! Is there a known way to chain detecting touch events? For example I'd like to

detectTransformGestures

and also

detectTapGestures

with double tap.

Hi, I'd like to highlight this bug as I cannot figure out a workaround and it's generating support requests (I work on a banking app). The gist is that the "LG Keyboard" app doesn't show a decimal separator without

TYPE_NUMBER_FLAG_DECIMAL

set, which doesn't appear possible via

TextInputService

on Android. https://issuetracker.google.com/issues/209835363

The

package androidx.compose.ui.res

provides access to resources as follows (src):

@Composable
@ReadOnlyComposable
private fun resources(): Resources {
    LocalConfiguration.current //<---- why?
    return LocalContext.current.resources
}

☝️ I wonder why a call to

LocalConfiguration.current

is needed before accessing the

resources

field. Is this a pattern which I should follow for any values provided with local composition? 👇 So should I do this in my own code?

@Composable
@ReadOnlyComposable
private fun myThing(): MyThing {
    LocalThings.current //<---- why?
    return LocalSomeThings.current.myThing
}

For a component like Accompanist HorizontalPager, the docs state

Pages in both

HorizontalPager

and

VerticalPager

are lazily composed and laid-out as required by the layout. As the user scrolls through pages, any pages which are no longer required are removed from the content.

Does this mean it is safe to use LaunchedEffect as a signal that the current page is just been shown? Or do they get created eagerly when user is contemplating a scroll/starting a swipe? Should pager state change events be used instead?

Hi, I’m new to JetPack compose and I’m a bit confused with colors and themes in JetPack Compose. When I do:

Text(
        text = "Something",
        style = MaterialTheme.typography.body1
)

then color is wrong when Android is set to dark mode. It is somehow connected to `Surface`/`Scaffold`but it is still not working for me. Why it is designed in so counterintuitive way? It looks like I have to specify colors in

Typography

(which is solution I feel is wrong as colors should be in ColorScheme IMHO)

I have the following layout:

Row {
    ComponentA()
    Column(modifier = Modifier.fillMaxSize()){
        ComponentB()
    }
}

how can I align the ComponentB to bottom right of the Column? I'm trying to achieve something from the image attached

I am not sure if this was reported by someone else (I couldn't find anything) but I have a problem with

VisualTransformation

in

TextField

(even with

PasswordVisualTransformation

) Whenever

VisualTransformation

is involved the cursor disappears and cannot be moved by dragging. (video example)

Are there any known issues with using bottom sheets for dynamic content and/or user (keyboard) input? For example: A bottom sheet containing a search bar and a list of items which is filtered based on the search.

Is LazyColumn really performance effective? My LazyColumn seems to be to janky and lagging on scroll. Is there any specific case for it or is it just bad in general? Also are there any best practices for combination of views in LazyColumn?

I have a

View

variable inside a shared ViewModel which lives with in the app scope and not inside a specific route. I use this view inside one of my routes. My issue is that if the screen is rotated or the route is navigated to again from itself, loading the view throws an exception since the view is still attached to the previous layout parent. I know the fix for this is to have at least 2 instances of the view I need but the issue is that composable lifecycles work a bit weirdly and I cannot figure out exactly how and when I should tell the ViewModel to switch the used view so it wont throw an exception. More in 🧵

Seeing how LazyColumn seems to fully recompose on item change is there any interest in having each item collect a secondary state in case some day lazycolumn change it's implementation or is the cost of the collectasstate in each items > recomposing the whole lazycolumn from a single collectasstate ?

I am using

ModalBottomSheetLayout

and

BottomSheetNavigator

and I’d like my bottom sheets to open into

Expanded

state. The

HalfExpanded

state doesn’t really suit my use case as there is often a lot of content in the sheet, and/or the keyboard is up. But, curiously,

ModalBottomSheetState.expand()

is

internal

and it’s not obvious to me how I could manipulate

SwipeableState.anchors

. Any advice? Thanks!

Hey all, why is this coming up as a val?

The intrinsic size of images loaded from a file is null which is causing a Image to have a height of 0. Is there a way to have the height of an

Image

match the aspect ratio of the image loaded?

Are

firstBaselineToTopHeight

 &

lastBaselineToBottomHeight

(TextView attributes) available in Compose?

Hi All, on material3, there is no option to dock floatingActionButton to the bottomBar, doesn’t it mean it is no longer recommended to do so ? Also on the new 

androidx.compose.material3:material3:1.0.0-alpha02

  

scaffoldState

  has been removed. Does it mean in the future we will no longer be able to launch a Snackbar and link it’s state to the Scaffold?

Do folk have any smart ways of discovering what causes a recomposition? My ideal would be some log that says 'Because <name> state changed at <file:line>'? My use case is debugging 'jank' in

AnimatedContent

transitions because multiple recompositions are firing where conceptually there should be only one. Carefully tracing the code for state changes is a given, just wondering if people can share any smart breakpoints/profiling tricks they're employing?

Which is the better own dialog component in Jetpack Compose?

@Composable
@Deprecated("Example with bug")
fun ListWithBug(myList: List<String>) {
    var items = 0

    Row(horizontalArrangement = Arrangement.SpaceBetween) {
        Column {
            for (item in myList) {
                Text("Item: $item")
                items++ // Avoid! Side-effect of the column recomposing.
            }
        }
        Text("Count: $items")
    }
}

I don't know why this code has thread-safe problem, can anyone explain ? https://developer.android.google.cn/jetpack/compose/mental-model#parallel

How can I automatically reduce fontSize if the text overflows? Im using onTextLayout and didOverflowWidth, but its always false even though my text clearly overflows!

any reason why I can’t find the

weight

Modifier? just goes unresolved, no hint to import or anything, using Compose

1.0.5

How to reach same behavior in Compose like MATCH_PARENT in View Framework behave? modifier

fillMax...

looks pretty the same, but when it applied to child of container, that doesn’t have exact size, then child stretch the parent when i used view framework i can did like

parent(wrap_content) {
   child(match_parent) // 1
   child(exact_size) // 2
}

and size of

1

was always the same as size of

2

. And when size of

2

changes size of

1

changes as well. Can i do the same in Compose?

Is there a way to make a LazyColumn scrollable in preview? currently my preview content is larger than the preview size and there’s no way to scroll it.