And how to pass Parcelable using compose navigation?

Is there a more basic version of

BasicTextField

? 😅 I don't want to show the string that was entered as a text.

Hi, is there a way to make the bottom sheet fully expandable and completely hide, I want to avoid the half expanded State with the new Navigation Material library?

Does anybody know what happened to DataTables which were, e.g., described and used here: https://proandroiddev.com/jetpack-compose-data-tables-33a247f59fd5 I am definitely missing such a thing.

Hey, do you know if there is a way in compose UI tests to check if an icon is displayed ?

Hello, does someone has an Idea about how to count lines of a string in order to show or not see more button using compose like on the following screenshot ?

Since Compose splits the machinery and the UI, how complicated would it be to create adapt Compose for other frameworks? Let's say I'm writing something directly with OpenGL and I'd like to use Compose with it. Is it just a matter of reimplementing all Composables (which there are a lot of, so it would take a lot of time) or is there actually something complicated that ties Compose to Skija/Skiko?

Why does my timer's number get delayed when I use

if

or the

compose animation api

to control whether a screen is displayed or not?

So I absolutely love this widget from the Google Podcast app, and I’m wondering if anyone has any advice on how I could go about implementing such a widget in Compose? I might be a bit out of my depth on it, but if anyone has any advice or places to start I’d greatly appreciate it.

I'm not really getting the point of this default surface in a new Compose Activity. What's it's purpose? And why does it set the background color?

Is there a way to grab the NavController like a singleton? I have an async api call that I want to switch screens if returned ok. Right now I have to physically pass the nav controller into the async cb and it would be alot cleaner if I could call it back as a singleton when ever I needed it in my code.

What would be the recommended approach to error handling text input in a composable show below? I could define an interface for the textfields that handle number input, and implement it based on whether it needs input validation but I am unsure if that is a good approach. Code in 🧵. ``````

hi guys, I had a problem with compose and navigation. I have 2 screens, splash screen, stimulate delay some time and then navigate to home screen. it navigates normally but home screen blinking and I found splash screen is recompose again again. So this is problem from compose or my implementation is wrong? Please help me!!!

what's new in

compose 1.0.1

?

If there’s some clickable element in front of scrolling container, it seems like this element intercepts touch events, and container doesn’t scroll. Is there workaround for this behaviour? Code and video in 🧵

This message was deleted.

Hello, I am getting this warning when I a compile a brand new android project that uses compose 1.0.1 and kotlin 1.5.21:

w: ATTENTION!
This build uses unsafe internal compiler arguments:

-XXLanguage:+NonParenthesizedAnnotationsOnFunctionalTypes

This mode is not recommended for production use,
as no stability/compatibility guarantees are given on
compiler or generated code. Use it at your own risk!

I would like to use compose in production and I am just wondering if I should be worried about this.

Hi everyone, Just would like to clarify something about

derivedStateOf

. In the official Documentation here: https://developer.android.com/jetpack/compose/side-effects There is this sample code:

@Composable
fun TodoList(
    highPriorityKeywords: List<String> = listOf("Review", "Unblock", "Compose")
) {
    val todoTasks = remember { mutableStateListOf<String>() }

    // Calculate high priority tasks only when the todoTasks or
    // highPriorityKeywords change, not on every recomposition
    val highPriorityTasks by remember(todoTasks, highPriorityKeywords) {
        derivedStateOf {
            todoTasks.filter { it.containsWord(highPriorityKeywords) }
        }
    }

    Box(Modifier.fillMaxSize()) {
        LazyColumn {
            items(highPriorityTasks) { /* ... */ }
            items(todoTasks) { /* ... */ }
        }
        /* Rest of the UI where users can add elements to the list */
    }
}

Wouldn’t the same thing would be achieve even without the

derivedStateOf

? Like:

@Composable
fun TodoList(
    highPriorityKeywords: List<String> = listOf("Review", "Unblock", "Compose")
) {
    val todoTasks = remember { mutableStateListOf<String>() }

    // Calculate high priority tasks only when the todoTasks or
    // highPriorityKeywords change, not on every recomposition
    val highPriorityTasks by remember(todoTasks.value, highPriorityKeywords) {
        todoTasks.filter { it.containsWord(highPriorityKeywords) }
    }

    Box(Modifier.fillMaxSize()) {
        LazyColumn {
            items(highPriorityTasks) { /* ... */ }
            items(todoTasks) { /* ... */ }
        }
        /* Rest of the UI where users can add elements to the list */
    }
}

Wouldn’t this do the exact same thing?

❓ Where can i find that sample? 🤔 I’ve looked at cs.android.com

* @sample androidx.activity.compose.samples.BackHandler

I have a weird problem related to Dialog or Popup, I have a screen that shows a lazy list of cards when I click on a card I display a Dialog that among other things allows to scroll up and down the aforesaid list. But after randomly 2,3,4 times the whole dialog is closed without passing by the onDismissRequest handler. If I call the code that produces the scroll in for example the topApp Bar then everything is ok.

How might you implement drag velocity… Like the scroll fling behavior in a scroll view? I have detectHorizontalDragGestures working, but I’d love to have some continuous movement in a widget that I’m building after you stop dragging.

Does anyone's compose previews work with the latest stable version I keep seeing

PreviewActivity is not a subclass of Activity

Hi all. I have strange behavior with TextField and keyboard. When i open activity and tap to field i see keyboard and it hides field. But if i close keyboard and tap again all works fine and works as ajustPan. What can be wrong? I use simple column with verticalScroll param and some text, switches and TextFilds widgets.

Whats the best way to get two columns to stick to the left and right side of a row?

In jetpack compose how do you use timers? I have a progress bar that I want to continuously cycle until I get a response back from my servers. I was googling a bit but not getting much useful info. Maybe timer or clock isnt the right name to google?

EDIT: Solved this, solution in 👉 🧵 I'm integrating a

TextField

and

DropDownMenu

to make a fairly standard drop-down selection for a form. For this I want to suppress the standard text-editing interaction with the

TextField

and just respond to clicks by opening the menu. Found this becomes a bit of a catch 22 though: • Keeping the

TextField

enabled, and trying to apply an overriding

clickable

modifier to it, or its parent, does not stop the TextField from capturing user interaction and behaving normally, as hoped. • Disabling the TextField and applying

clickable

to its parent gives desired behaviour, but then of course the colours look disabled too, which I don't want. So I'm trying to apply new

TextFieldColors

to it, that maintain the enabled appearance. However I'm not finding this straightforward either - trying to reference the existing default colors gets you tangled up in interaction sources and stuff which does not feel necessary to be doing. Any 3rd way I'm missing?

A design fault in Compose themeing/coloring 🤔 ? Why does

LocalContentColor

always default to black, and this default is not overridden by a

MaterialTheme

block? This means that even in Dark themes, the text colour inside a

TextField

, for example, is also black, leaving it hard to read. The API comments talk about this being 'typically' set to

MaterialTheme.onSurface

- but don't say whether this is the direct responsibility of the developer, or how to do it. This feels like something I shouldn't be handling directly - why do other Material elements adjust well to dark/light scheme, but the text inside a

TextField

does not? Either I'm missing something or this is inconsistent/broken? Edit: Straw-man solution 👉 🧵

How to make Autosizing Text in compose

hello how to set drawable to button as background