I'm really confused about

.observeAsState

. In my ViewModel I have this:

val dynamicCallSenderCode = MutableLiveData(0)

     fun onSenderChanged (){
        dynamicCallSenderCode.value = broadcastReceivers.notifyCallSenderCode(context)
    }

What I want to do is observe the broadcast receiver changes from my HomePage but I can't use

.observeAsState

with a function. How could I pass these changes live to my Composable?

Can we pass Composable function as a constructor argument of a Class ?

Hi @Ian Lake, I was wondering if this is an intended behavior?

@ExperimentalAnimationApi
@Composable
fun FillingIssues() {
    val navController = rememberNavController()

    val number by sampleFlow.collectAsState(initial = 0)

    Scaffold(
        topBar = {
            // This recomposes just fine
            // Gets 0, 1, 2, 3
            Text(text = "Top Bar: $number")
        }
    ) { padding ->
        val modifier = Modifier.padding(padding)
        NavHost(navController, startDestination = FIRST_SCREEN) {
            myNavigation(modifier, number)
        }
    }

}

fun NavGraphBuilder.myNavigation(
    modifier: Modifier,
    number: Int,
) {
    composable(FIRST_SCREEN) {
        // This Doesn't recompose
        // So it remains displaying
        // Number: 0
        // Even when 1, 2, 3 are emitted
        // This only happens when I make it
        // as an extension function
        Column(
            modifier.fillMaxSize(),
            Arrangement.Center,
            Alignment.CenterHorizontally
        ) {
            Text("Number: $number")
        }
    }
}

val sampleFlow = flow {
    emit(1)
    delay(1000)
    emit(2)
    delay(3000)
    emit(3)
}

private const val FIRST_SCREEN = "FIRST_SCREEN"

Hi, what you see are 2 Composables 1. Conversation - LazyColumn representing messages (I used modifier .fillMaxSize() to fill all the rest of screen) 2. UserInputBar - multiline Text Field surrounded by Surface that wraps around this text field so it increases it's size when text input goes multiline I connected these pieces with use of ConstraintLayout. Bottom of Conversation composable is constrained to top of UserInputBar, but it looks like it's actually constrained to middle of UserInputBar so composables overlap themselves. Does anyone know how repair such behaviour?

Is there a way to reinstall

pointerInput

? It doesn’t react on lambda changes and always use only first served lambda. Below prints only

pointerInput 2

and doesn’t print anything on switch toggle.

@Preview
@Composable
fun PointInputTest() {
    var toggled: Boolean by remember { mutableStateOf(false) }
    Column {
        Switch(checked = toggled, onCheckedChange = { toggled = !toggled })
        Box(
            modifier = Modifier
                .size(50.dp)
                .background(Color.Red)
                .run {
                    if (toggled) {
                        pointerInput {
                            println("pointerInput 1")
                        }
                    } else {
                        pointerInput {
                            println("pointerInput 2")
                        }
                    }
                }
        )
    }
}

"LazyColumn/Row is the Compose equivalent of RecyclerView" ... Awesome! With RecyclerView, we can use

ListAdapter

and

DiffUtils.ItemCallback

to get automatic cool animations when items in our list change positions and are added/removed ... Is there a way to achieve this with LazyColumn?

I wrote a little abstraction to render some content (a series of Text composables) either horizontally (Row) or Vertically (Column). Does Compose offer a better (built-in) way to do this?

enum class Orientation {
    HORIZONTAL,
    VERTICAL
}

@Composable
fun OrientedContent(
        orientation: Orientation, 
        modifier: Modifier = Modifier, 
        content: @Composable () -> Unit) = when (orientation) {
    Orientation.HORIZONTAL -> Row(modifier = modifier) { content() }
    Orientation.VERTICAL -> Column(modifier = modifier) { content () }
}

Hi again, I was wondering why this code is not updating the color of my buttons in real time. I'd be grateful for some pointers, thanks!

Hi again! I'm running into a problem with lists. I have a remembered

mutableStateOf()

a mutable list of strings. I'm just using a forEach inside a column to display the items.

messageList.forEach {Text(it)}

However, I don't seem to see any updates on the screen when the list gets a new item (The list is updated via a coroutine scope fetching data from elsewhere). I put a

println()

to debug, and the list definitely changes in size - so I think I must be doing something wrong

Shouldn't

val vm: MyViewModel = viewModel()

always retrieve the same ViewModel object in different composables but in the same activity?

Hello, sometimes when I'm trying to extract a smaller composable from a larger composable using android studio's refactor "extract method" I will get error messages like this

Function ColumnScope.weight(Float, Boolean) on Modifier will no longer be accessible after extraction

Is there a way around this?

When I call this composable I get two messages: ... Slider onValueChange: 10.0 ... Slider onValueChange: 5.0 I was expecting only one callback, the second one.

@Composable
fun SliderTest() {
    val sliderValue = remember { mutableStateOf(5f) }
    Slider(
            value = sliderValue.value,
            onValueChange = {
                Log.d("Slider onValueChange ", "$it")
                sliderValue.value = it
            },
            modifier = Modifier.width(200.dp),
            valueRange = 0f..10f,
    )
}

The first message is always for the end value in valueRange, 10 in this example. (I'm using Arctic Fox 2020.3.1 Canary 4, built on Dec 23, 2020.)

When will alpha11 be released？ I can't wait😝

I would like to show a vector image within my composable for a specific period of time, e.g. 3 seconds and it should block so nothing else is done while it is displayed. Is this possible?

I using paging with Compose but it crashes the app on orientation change, but with the normal list, it's work fine.

--------------------- in ViewModel ---------------------------- 
val newsSelection : MutableStateFlow<HeadlinesPagingKey> = MutableStateFlow(
            HeadlinesPagingKey())

@ExperimentalCoroutinesApi
     val topHeadlines: Flow<PagingData<Article>> =
             newsSelection.flatMapLatest {
                 newsRepository.topNewsHeadlines(it)
             }.shareIn(viewModelScope, SharingStarted.Lazily,1)

---------------------and in Composable---------------------------- 

val lazyPagingItems: LazyPagingItems<Article> =
        headlinesViewModel.topHeadlines.collectAsLazyPagingItems()

Hi, Is there a way to get the value of the y position while the screen is scrolling? I have a situation like this:

LazyColumn() {
    item {
      box()
      box()
      box()
      ScrollableTabRow()
    }
    itemsIndexed {...}

I need to know when the ScrollableTabRow moves past a certain position on y axis (for example lets say 100.dp ) I tried working with .scrollable() (something like scrollable) and with scroll gesture filter (something like gesture) and with dragGestureFilter but i cannot get it to work, am i doing something wrong, or is it just not possible?

Question: Do I need to call compose from the same coroutine every time? My Textfield is generating random input based upon previous entered characters. When I enter for example type "email@123456.com" then remove everything and then type "thisis" it copletes with "thisis@124356.com". I do submit my input to a multithreaded application (using MVIKotlin) but I would expect it would then complete to previous entered values instead of the characters in random order. Am I missing something?

Is mandtory that composes uses AGP 7.0.0-alpha04? It looks that it needs java 11, and jitpacks not works on my repo

Error log: https://jitpack.io/com/github/alorma/Compose-Debug-Drawer/0.1.0-beta-06/build.log Repo: https://github.com/alorma/Compose-Debug-Drawer/

I have Compose code in a separate module. When I try to add the Compose module to the main module, the

androidx

libraries get bumped to alpha for the whole project. Anyone know what I’m doing wrong?

Hi all. I’m looking to draw a composable and all of its content into a Bitmap for screenshot testing, including stuff currently scrolled outside of the bounds of the device window. Is it possible?

Hello everyone. I have a question about fullscreen composables. While using Scaffold (and its bottom bar for navigation) and NavHost (attached to the bottom bar) together, opening a fullscreen composable from a content composable of Scaffold fills the content composable’s area as expected. To open them fullscreen covering the whole, another NavHost should be placed on the layer above the Scaffold in order to get rid of the scope of content composable.* However, I do not want to include all fullscreen pages in the same NavHost as it violates my architecture. In order to place fullscreen composables in their respective packages (not including them in one nav host), I have customized Scaffold whose bottom bar is stateful just like in  BottomDrawerLayout. I am hiding/showing bottom bar while navigating to fullscreen composables from the content composable of the Scaffold by the NavHosts inside the content composables. Though it supported my architecture, it feels like I am breaking the KISS principle 🙂 Do you have any other suggestions? (*One of Jetpack’s example apps Jetsnack has an example usage of Navhost used for fullscreens in git branch dedicated to navigation. You can check it out if you’re interested in the topic)

Is it possible to navigate between activities? and have the bottom bar work? seems like the answer is no (for now?)…

Is there a way to compute

TextLayoutResult

before the text is actually drawn? I reduce my text size until the text fits the width of the screen using

onTextLayout

(never thought it'd be that easy on Android) and it works fine but I'd like to do it in background without the user seeing the text get smaller.

Did someone have any success combining Kotlin 1.4.21-2, Multiplatform, Serialization and Compose in one module? I think I tried configuring it in every possible way (known to me) and there is an issue during build

Back-end (JVM) Internal error: Couldn't inline method call '<get-current>' into @androidx.compose.runtime.Composable

Hi, about using Paging 3 with Compose and keeping the scroll state while using Navigation, I made a one-file sample and found out it works if I do the

collectAsLazyPagingItems()

before declaring the

NavHost

but it seems to me like I should be able to do it right before

LazyColumn

Is there something I’m missing ? (I’ll share the code in the thread :thread-please: )

The docs for

AmbientAutofillTree

note that Autofill semantics will be replacing some of the existing autofill APIs at some point, but reference an internal issue and the comment itself seems to be over a year old. Is the plan still to leverage semantics for some of the autofill support? Ref: https://cs.android.com/androidx/platform/frameworks/support/+/androidx-master-dev:co[…]compose/ui/platform/Ambients.kt;l=58-65?q=AmbientAutofillTree

Anyone used product flavors with Compose? In particular I'm curious about best practices for building out different theme colors for different product flavors

Is there anything wrong in having one big state object for the whole application? I am already doing that and everything works great. I just wonder if there are any performance problems in case the app grows too big. I am defining the state of each screen as a separate data class object, which is instantiated as a property of the big state object.