Hi guys! I’m having some weird issue with Gboard with auto correct enabled and TextField It happen If I use

TextFieldValue

var text by remember { mutableStateOf("") }
TextField(value = TextFieldValue(text), onValueChange = {text = it.text})

Hi. I'm trying to create a

Table

composable that displays data in rows and column of variable width/height. So far I managed to lay out the table using a `Layout`(image 1). The cells are placed properly, but not measured properly, because I gave up on trying to understand and implement intrinsic measurements. I need to add the grid to the table but if I try to use the cells to do so, the borders are not aligned since the cells are not measured properly (image 2) Is there a way to draw directly on the Layout using the same coordinates I used to place the cells?

What is the correct way of disabling screen interaction when

CircularProgressIndicator

is materialized on screen.

Box(
    modifier = Modifier.fillMaxSize(),
    showLoading:Boolean,     
  ) {
    LazyColumn { // displaycontent
      
    } 
    if(showLoading){ // disable background screen interaction
       CircularProgressIndicator()
    }
  }

Hi! I am currently working on an aap with all composables (No fragment) with single activity, I am little confuse about navigation compose. If in future, I have to use fragment in this app, can I navigate from a composable to a fragment or How its work?

I've got text like this

Text("first line\nsecond line")

but it just shows the \n directly in the Text widget According to SO, I should do

Text("first line\r\nsecond line")

but that didn't work either. Any thoughts? Edit: nvm did this and it works now

myText.replace("""\n""", "\n")

Hello! Is it possible to specify color only for one side of border?

Shouldn't their be an option to extract a composable to a function? or am i missin somethin

Is it bug or feature? When TextField disappears it triggers

onValueChange

Hello! I want to set focus on input and show a keyboard when the screen is showed. I want to implement this behavior on a number of screens and I want to reduce code duplication with FocusRequester and LaunchedEffect. Is it correct to create requestFocus modifier like this?

fun Modifier.requestFocus(requester: FocusRequester = FocusRequester()): Modifier = composed {
    LaunchedEffect(requester) {
        requester.requestFocus()
    }

    focusRequester(requester)
}

What do you guys think about adding some compose into your data models? 🤔

Is there an available composable text field that allows user input while also showing a trailing value? For use cases where the user is entering the user name portion of an email address, or the subdomain in a domain name, and you want to show the trailing domain. Like this:

User can input text on the left of this text field, and "<http://example.com|example.com>" stays visible as the user is typing
________________________________
|<user input here> .<http://example.com|example.com>|
--------------------------------
Alternately the "<http://example.com|example.com>" could be outside the text field:
___________________
|<user input here>| .<http://example.com|example.com>
-------------------

what is the safe way to show old-style android dialog from Composable function? For example:

@Composable
fun ScreenContent(state: State) {
  if (state.showDialog) {
    // Need to show MaterialDatePicker here
  }
}

Use

SideEffect

?

Can i leverage compose runtime on kotlin multiplatform iOS targets via

expect / actual

?

Hi, what is the best way to handle a

LongClick

on a

TextButton

Is it possible to animate the constraints of a constraintLayout in compose?

how to convert Compose View to Bitmap?

How could one go about creating a text field which supports Undo Redo !

So I've searched a lot about @Immutable / @Stable but I have an hard time to understand the cases when it's properly inferred or not. I have data classes that are shared with non compose apps so I'd prefer not to add compose-runtime to those modules. But I do not really understand if it's currently possible to wrap then with no cost or help compose without those annotations.

[✅ SOLVED] ✨ Animation:

expandHorizontally

and

shrinkHorizontally

accept a param named

expandFrom

and

shrinkTowards

respectively. But it looks like it doesn’t consider that param. OR am I doing anything wrong? More details inside 🧵

Consider the map:

@Composable fun MyComponent(map: Map<Int, String>) {
   val states = map.mapValues {(k,_) -> remember(k) {mutableStateOf(0) } }
   for ((k,v) in map) MyStatefulComponent(v,states[k]!!)
}

On a first look, this looks fine. We host the states for

map.size

items of

map

in a parent component

MyComponent

, and create

map.size

child `MyStatefulComponent`s, each with its own state. However, on a second look, this code makes no sense. The way

remember(key)

works, is that whenever a new value is passed, the state is erased and something new is remembered. So if there are at least two elements, the state of all elements except the last one will be erased. In practice, hocus pocus, it works. Each element of

map

has its own unique state cell. No clue how. If a child gets added to or removed from

map

, it updates and keeps working. Magic! But, in my case that I can't reproduce here, the state gets deleted whenever the map shrinks. So I want to understand: what actually makes this work?

If you use a

Shadow

in a

TextStyle

and the

blurRadius

is

0

then the shadow doesn't appear. Is that intended behaviour, do you think?

What is the best method to swith between 2 languages ( localization) ? Is there any example ??

I have seen a few times a method call is called twice like this https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:compose/[…]/runtime/Composer.kt;l=1742?q=internal%20class%20ComposerImpl or this https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:compose/[…]ime/Composer.kt;l=1235-1237?q=internal%20class%20ComposerImpl (not consecutive, but somehow a method is called twice. Maybe it is legit due to internal state change) Not sure it is a bug or something hidden inside?

Is there any way to apply the old style in existing app with compose like below

<style name="TextAppearance.TypographyStyles.Caption.Test">
        <item name="fontFamily">@font/roboto_medium</item>
        <item name="android:fontFamily">@font/roboto_medium</item>
        <item name="android:letterSpacing">0.0</item>
    </style>

[Q] I have the following layout:

LazyColumn(modifier = Modifier.fillMaxSize()) {
  item {
    Box(modifier = Modifier.fillMaxWidth().height(200.dp))
  }
  items(100) {
    Text(text = stringResource(id = R.string.long_text))
  }
}

When I scroll down, the Box is out of the screen, but not enough for it to be disposed. How can I tell that the Box is out of the screen or not without using LazyListState? (So something that works even when the LazyColumn is replaced by a scrollable Column).

Can somebody show me a simple example of

TargetBasedAnimation

? 🤔 (Maybe something with

Box

,

Text

etc 😬)

Pretty happy with this interaction, feels smooth

How do I create a form like this which can have the keyboard go to the next text field, and on the second text field, the keyboard essentially clicks the button?

For those implementing Accessibility w/ TalkBack - Are there any common reasons why TalkBack would not say the role of the component? All I get is: '<the button text>, double-tap to activate' whereas with the old View system it would say '<the button text>, button, double-tap to activate' <-- I need this for consistency ...I've tried setting the Role semantic, merging nodes, not merging etc. it just won't say 'Button' and it's driving me up the wall! EDIT: Solved but in an unexpected way - not sure if this is a bug - google folk?

this might be a silly question, but those of you who work on projects where unit tests are important but UI tests are much less common, what did you do when you started bringing in more and more Composables into your app? obviously the coverage drops significantly if you don’t write UI tests for everything because you now have a lot more kotlin code for Composables.. but I’m curious about what others have done. have you: • started being more strict about writing UI tests • not written UI tests and simply accepted the coverage % drop • something else?