I have a full Expanded 

ModalBottomSheetLayout

, when swipe it to the bottom to collapse it, it stops on Half Expand state and I need to swipe it again to collapse it totally, any idea?

I want to display a tree view (using standard

LazyColumn

), but because the tree itself is very complicated and reactive, I would also like to use compose-runtime to manage its nodes. I.e. I want to use the compose with custom `NodeApplier`to generate nodes of the tree that I then take and display with the standard (in my case desktop)-compose. Can it be somewhat easily achievable? There is something called

sub-composition

, the `Composition`function also takes a parent `CompositionContext`but I don't quite know how to glue that together. I have looked at https://github.com/JakeWharton/mosaic/ but it uses the compose-runtime standalone, while I want it kind of 'nested'.

I'm trying compose material3, I've read here that we are supposed to keep both Material2 and Material3 libraries together right now. I'd rather not, but I need an

OutlinedTextField

do you know of any library or snipped of code that port material 2 textfield to material 3? Thanks

Is it a known bug that on Samsung / Android 9 devices, when Talkback enabled, any Scrollable (

LazyColumn

,

scrollable

modifier) does not react to 2 finger scroll gestures at all? Easy reproducible with the very simplest

LazyColumn

demo (in Thread). I don’t experience this with other devices so far. Actually a dealbreaker for converting an existing App (which relies on accessibility) to compose, as I planned to 😞 Should I file a bug?

var readMore by remember { mutableStateOf(false) }
var clickText by remember { mutableStateOf("Read More") }
var showClickButton by remember { mutableStateOf(false) }
val annotatedText = buildAnnotatedString {
    withStyle(style = SpanStyle(color = MaterialTheme.colors.OnSurface800)) {
        append(text + " ")
    }
    
    if (showClickButton) {
        pushStringAnnotation("click", "click")
        withStyle(style = SpanStyle(color = MaterialTheme.colors.Interactive500)) {
            append(clickText)
        }
        pop()
    }
}

ClickableText(
        text = annotatedText,
        style = MaterialTheme.typography.smallBody,
        overflow = TextOverflow.Ellipsis,
        maxLines = if (readMore) Int.MAX_VALUE else 2,
        onTextLayout = { showClickButton = it.hasVisualOverflow }
    )

I am trying to “Read More” button at the end of text view but looks like

buildAnnotatedString

does not recompose when

showClickButton

or state change, so here how can i achieve this ?

Anytime the Compose UI

View

is used as part of a transition, it will be detached from its window when the transition starts instead of when the transition ends, thus causing your composable to dispose of its state while it is still on screen.

What does this mean? why is Compose UI view detached from its window when the transition starts?

Has anyone here experienced

View.measure

crashes in Accompanist (probably accompanist-pager) starting on v0.19.0? Suspect it comes from the refactor to using a

LazyList

introduced in that version, and we're seeing it across multiple devices in production, but we're unable to reproduce it locally, and we're a little lost on how to debug this. 😅 GitHub issue: https://github.com/google/accompanist/issues/847

I'm writing E2E test with Compose. It works fine generally, however I'm testing deep links and the composeTestRule.activity keeps the old destroyed activity causing a crash if I try to access it after the deep linking action. Compose test APIs that don't use the activity work fine though. Should I file a bug?

Hi I’ve experimented with

Modifier.animateItemPlacement()

function of lazy list. There is a bug when we add an item to the first index of a lazy list which is full and scrollable at this moment. When it is not full added item is animated but when it is full it is not animating. As a workaround I added extra item to the top of lazy list via

item("hint") { }

I would like to be able to pan my canvas content with some inertia effect. Does compose have any concept or tools to achieve that? Searching for “inertia” in the context of compose did not reveal anything useful. (E.g., JavaFX has this built into gesture handling by default. https://openjfx.io/javadoc/17/javafx.graphics/javafx/scene/input/GestureEvent.html)

Can we exchange ideas about how to make `ViewModel`s independent of compose? I'm thinking specifically of

TextFieldValue

for forms. Say you need to control both the text and the selected state from the ViewModel. How do you handle this scenario?

I just marked the following class with

@Immutable

and now the app started crashing.

@Immutable
data class EqualSplit(
    val name: String,
    val image: String,
    val number: String,
    val selected: Boolean
)

The error log says:

java.lang.NoSuchFieldError: No static field $stable of type I in class EqualSplit; or its superclasses

What does this mean?

I have a list of data classes that I am displaying using a LazyColumn. But even when a single item in the list changes, all the items inside LazyColumn are recomposed. I thought marking the data class as

@Immutable

might fix the issue but it didn't. How can I prevent these unnecessary recompositions? Code in 🧵

I want to add spaces in text field. I’d did all what i can for achieve this, but looks like some kind of visual artifacts exists even after i ensure that offsets in

OffsetMapping

mapping correctly. I’ll add scratch in thread. Logic next When price entering then

filter

of

VisualTransformation

calls and i creating

Price

object. It contains three values integer(string, with spaces), fractional(string) and boolean describes is there comma or no. This object stores in my class, implements

VisualTransformation

and

OffsetMapper

. mapping of offset happens based on this object. It stores price (with spaces) and price payload. For example if

price

is

8 994,34

payload

should be

8994,34

(witout spaces). Based on this values i am calculating offset. I even simulate this in scratch file [screenshot] and all looks good. But in dynamic, when i interact with input - i see artifacts! i For example: when i try to backspace number then backspaced not the number, that i want to backspace, but backspace previous, but not always And then i understood. The problem is that offsets that i calculate is dynamic. That changes when integer length changes. Example

9 999

offset at position 2, and when i enter another digit whenever

99 989

offset now at position 3. So when i backspace digit offset positions also changes during editing. This situation can be solved?

using

Map

like:

mutableStateOf(map)

and reassigning that

Map

doesn’t trigger recomposition? how can I approach this?

Is there any sort of equivalent mechanism to

@DisallowComposableCalls

that I can apply to my own functions to not allow them to be called from inside composable functions? Or if not, any ideas on how to improve the developer experience regarding this: I have a function that looks like this:

inline val Int.dp: Int
    get() = (this * Resources.getSystem().displayMetrics.density).toInt()

That is used from normal non-composable functions, but is simply annoying as it always comes as a code completion suggestion when I’m inside composable functions, but in there I always want the

androidx.compose.ui.unit.dp

import instead.

Could one say Compose ui is more equivalent to flutter ui, than os native?

how to draw a vertical dotted line in

compose

?

If I have a

LazyList

with a column that contains several sub-items (e.g. inside a card). How can I optimize it such that the nested items arent recomposed all the time? Im seeing 3 recompositions each time the list is recomposed, taking up about 15 ms each; since Im also using a pager, the same process is repeated for pages to the left/right of the current one, effectively taking up 135 ms everytime the list recomposes.

Trying to run the

todoapp

inside

compose-jb

and getting the following error:

The minCompileSdk (31) specified in a

dependency's AAR metadata (META-INF/com/android/build/gradle/aar-metadata.properties)

is greater than this module's compileSdkVersion (android-30).

Dependency: androidx.compose.material:material:1.1.0-beta01.

AAR metadata file: /Users/alexander/.gradle/caches/transforms-3/137251a10d2c5151ea1d3a5bd29928e0/transformed/jetified-material-1.1.0-beta01/META-INF/com/android/build/gradle/aar-metadata.properties.

How do if fix this? I’ve tried

clean

->

build

and “Invalidate cache and restart”

Hi @Ian Lake, Any guide on how to provide Navigation Animation with Accompanist for Nested Navigation? I tried doing:

navigation(
   route = "routeName",
   startDestination = "startDestination"
) {
   // transitions defined in this composable never seem to run
   composable(
        route =  "someDestination",
        enterTransition = { slideIntoContainer(AnimatedContentScope.SlideDirection.End) },      
        exitTransition = { slideOutContainer(AnimatedContentScope.SlideDirection.Start) },      
        popEnterTransition = { slideIntoContainer(AnimatedContentScope.SlideDirection.End) },   
        popExitTransition = { slideOutContainer(AnimatedContentScope.SlideDirection.End) },
   ) {
      ...
   }
   ...
}

Is Play Store automatic robo testing still clicking around and navigating the app randomly? My app shows an AlertDialog with two buttons when first launched and for the past few releases the robo testing only starts the app and idles around for a minute. Wondering if it's something on my end or has anyone had similar experience.

What is the road map for compose to support Kotlin 1.6.0?

Compose 1.1.0-beta03 freezes on ComposeView. I don't see any logs, but the issue seems to be same as https://kotlinlang.slack.com/archives/CJLTWPH7S/p1620052815345200 it happens very randomly, but quite often. I will see if downgrading or changing some other dependencies will work. Do you have any idea how to debug? The UI thread isn't busy, just doesn't accept any inputs and if I use a navigation drawer which can switch between compose view fragments, it starts working again.

Is it possible to modify

animateContentSize

to expand the component from the center instead of from the left to right?

Is there a way to call a specific composable from a notification? I know how the open an activity, but I'm trying to access a specific screen (the same way you would do it with a navhost)

What are the diffs between

coordinates.positionInRoot()

and

coordinates.positionInParent()

?

Has anyone updated their project to Kotlin 1.6 with compose successfully? Trying to update now and getting this error from one of our modules:

e: This version (1.0.5) of the Compose Compiler requires Kotlin version 1.5.31 but you appear to be using Kotlin version 1.6.0 which is not known to be compatible.  Please fix your configuration (or `suppressKotlinVersionCompatibilityCheck` but don't say I didn't warn you!).

How do I get proper

fillMaxWidth

inside sth with `horizontalScroll`(by default it is ignored)? I simply want the background to span all available width.