Is there a way already to remove inside padding of TextField?

Anyone else experiencing Android Studio 2021.1.1 Patch 2 freeze on rendering a compose preview? I’m on an M1 Macbook pro which might be part of the problem.

Hi everyone, do you notice Lazy Columns do still have a lot of jank even now if the layout is fairly complex like a social media card… I ve disabled all animations and I still see jank… I feel its because the paging compose version is on alpha : https://developer.android.com/reference/kotlin/androidx/paging/compose/package-summary

Hi, Code coverage with composable functions seem to be off using Jacoco. Any idea? Details in 🧵

Is there anything that helps with understanding what caused a recomposition, or why a

@Compose

function is not being skipped?

I had been interested in making a part of my composable App keep the screen awake. Reading though these docs it shows that all the approaches include either an Activity, or services etc. has anyone had to do this before? Any ideas on how to approach it?

Hello, I am using

Layout

to wrap 2 buttons to create a custom layout, one is

OutlinedButton

and another is

Button

. But when I pressing on the

Button

, the whole custom layout starting flash, it seems the whole Layout keep recompose(I add the log in Layout’s MeasurePolicy lamda and it keeps printing). However, it doesn’t happen if I press on

OutLineButton

. How could I avoid this? Thanks. It only happened when I wrap the Button in another Composable, if I just use Button directly(in first level), no issue Is it because when button is pressed, the size change so trigger some recomposition? I found the root cause, if set Button’s

elevation

to

null

, the problem is gone. But is there method that keep elevation and let Layout works as expected? 🤔

I’m trying to debug some piece of code. I narrow it down to this click listener:

val onItemClicked = { index: Int ->
    listInfoState.animateScrollToItem(index)
}

Why would this cause the excess recomposition i am having, without evening triggering the click ?

I am trying to use compose Paging with

collectAsLazyPagingItems

. Everything works fine until I scroll to a position which is bigger than the pagingSize and then I call

invalidate()

to get the pager data to reload. After this the

lazyItems

first only reloads the data for the visible viewport. My problem is that the

rememberLazyListState()

is not calculating the right position in this case and the scroll position is wrong. When I delete an item from the first half of the list that is < pagingSize then everything works fine. Is there something like:

rememberPagingLazyListState()

or am I making a mistake and it is supposed to work with

rememberLazyListState()

?

How can we show ModalBottomSheet using Compose Navigation? This is how my Modal sheet looks like:

fun AddressPicker(
    sheetState: ModalBottomSheetState,
    onConfirm: (Address) -> Unit
) {
    ModalBottomSheetLayout(
        sheetState = sheetState,
        sheetContent = { AddressForm(onConfirm) }
    ) {}
}

Then I added this into my nav graph:

composable(route = Screen.AddressPickerScreen.route) {
    AddressPicker(sheetState = sheetState) {
       // ...
    }
}

And to show it, I used below code:

navController.navigate(Screen.AddressPickerScreen.route)

Instead of showing the sheet content, it shows a blank canvas. What am I doing wrong?

While testing my code, I got confused about Recomposition. If I have a code like below, then what happens to

value

?

var value = false
SomeComposable { item -> // content block
  if(item) value = true
  // etc.
}

SomeComposable internally runs for loop. Will it run like normal for loop? Will

content block

recompose by itself, making

value

inconsistent?

Hi all, regarding includeFontPadding related changes b/171394808 in Version 1.2.0-alpha05, we’d love to hear your opinions and the impact on you. If you can give it a try better-er. Please let us know. aosp/1993911 has some screenshot updates showing the difference (it is mostly subtle). This prevents users to do things such as this b/171394808#comment32

Facing recomposition issue, more in the 🧵

What should I use to achieve this anim?

Is there something special that has to be done to release a compose aar library? We’ve done that privately, but none of the compose functions can be accessed / found. We just end up with build errors.

Does anyone have any recommendations for making an AndroidView update a MutableInteractionSource? I want to be able to track focus events from the legacy view in Compose code.

Quick technical question, is there any reason why clickable events being propagated through a box will travel through elements until it reaches a clickable? I.e. my touches seem to phase through views that are above another. This has probably been answered, but figured I’d ask

Is there a rule of thumb to choose

Column

with

Modifier.verticalScroll()

or

LazyColumn

? Seems for every scrollable page we can just use

LazyColumn

, but the `item {}`makes the development a little bit cumbersome, can I just use

Column

for the pages which don’t have infinite scrollable content?

I’ve compose hierarchy like below, que is NoteListComponent is querying db unnecessarily when I goto detail and come back (because of launchedEffect) is there any way I can ignore unwanted db queries ?

NoteListComponent(
notes: List<Note>
…coupleOfParameters
) {
    var searchText by rememberSaveable { mutableStateOf("") }

    LaunchedEffect(key1 = searchText) {
        notesViewModel.searchNotes(searchText)
    }
    LazyList(...withParams)

}

I am trying to access my room database viewModel in a Repo file rather than a Composable, because I want to use some data in my MainViewModel. I am getting a mismatch when trying to access the viewModel. What could I be doing wrong? It works absolutely fine when I call it within a Composable. I'm getting this: "Unresolved reference. None of the following candidates is applicable because of receiver type mismatch: public inline fun <reified VM : ViewModel> ComponentActivity.viewModels(noinline factoryProducer: (() → ViewModelProvider.Factory)? = ...): Lazy<TypeVariable(VM)> defined in androidx.activity"

My TextField gets hidden behind Keyboard. How do I avoid it? I am able to solve it by below snippet added to my activity.

android:windowSoftInputMode="adjustResize"

But if my

TextField

is inside a

ModalBottomSheet

, then this doesn't work. What should be the fix for this?

Documentation says - https://developer.android.com/jetpack/compose/lifecycle#skipping All primitive value types, strings and lambdas are

Stable

- as they are declared immutable. When declaring a data class or a class which can hold an immutable read-only list, should we mark it as

Immutable

as data-structures are not Stable by default? Or compose compiler can infer?

@Immutable
data class MyClass {
 val someId:Int,
 val myList:List<SomeClass>
}

[SOLVED] I’m using m2 text field. The text is being positioned in wrong position. It must be centered vertically

[SOLVED] Seems to be the newly built in navigation padding animation has a bug

Any idea what would cause a shadow around card composable appear with like a thick black border? In the preview or if I try the same in another app, it looks correct 🤔

Card(
    shape = RoundedCornerShape(8.dp),
    elevation = 10.dp
)

Is there anyway to observe

BottomSheetScaffoldState

? i would like to perform an action when its state is

BottomSheetValue.Collapsed

I tried using LaunchedEffect but it is not triggered

val bottomSheetScaffoldState = rememberBottomSheetScaffoldState(
                bottomSheetState = BottomSheetState(BottomSheetValue.Expanded)
            )

            SomeComposableWithBottomSheet(state: BottomSheetScaffoldState)

            LaunchedEffect(bottomSheetScaffoldState){
                if (bottomSheetScaffoldState.bottomSheetState.isCollapsed) {
                    onBackPress()
                }
            }

[✅ SOLVED] Subject:

rememberUpdateState

I’ve seen most of the

@Composables

are using

rememberUpdateState

before invoking a lambda. For eg,

BackHandler

internally calling

rememberUpdateState

on

onBack

lambda,

clickable

modifier calls on

onClick

lambda. Does that mean we should wrap all lambda with

rememberUpdateState

before invoking ? 🤔 If that’s the case, why can’t compiler do it for us? #possibly_a_stupid_question

This is bad right?

@Composable
fun SomeScreen(
    viewModel: SomeScreenViewModel = hiltViewModel(),
    someIdINeed: String = ""
) {
    viewModel.init(someIdINeed)
    MyActualScreenContent()
}

The viewModel.init(id) should go inside of a remember{}? Or is it better to do LaunchedEffect(Unit)? edit: I almost wonder how viable it'd be to create a lint rule or something that would flag this sort of stuff in a composable. The above code was in our codebase for like 3 months before i noticed it just now.

How do you achieve a keyboard that only allows numeric input? no dots, dashes, only 0-9

KeyboardType.Number

still allows special characters while

android:inputType="number"

doesn't