Hi guys what is recommended way of using

Spacer

in jetpack compose?

Spacer(modifier = Modifier.height(16.dp))

v/s

Spacer(modifier = Modifier.preferredHeight(16.dp))

what is the difference between

height

and

preferredHeight

?

This message was deleted.

Is there a more standard way of accomplishing this in Compose? (My very React inspired solution for holding a reference to a value across renders)

data class Ref<T>(var current: T? = null)

@Composable
fun SomeCmpt() {
  var jobRef = remember { Ref<Job>() }

  ...
}

Why can I set the

color

of

Text

, but not of

ClickableText

?

I’m curious, has anyone found a better way to maintain View State between screen navigations, like scroll position, besides doing something like state hoisting?

One thing i’ve noticed after upgrading from compose 1.1.1 to 1.2.1 (along with a kotlin 1.7.10 bump) is that I can no longer do this:

val screens = listOfScreens.sortedBy {
            stringResource(it.label)
        }

it complains that i can’t execute the stringResource function outside of composable scope. Instead i have to do this:

val context = LocalContext.current
        val screens = listOfScreens.sortedBy {
            context.getString(it.label)
        }

I’m a little confused what has changed between either kotlin or compose that this became a compile error

Did anything significant change in AS Flamingo or Android 13 to improve Live Edit speed? A sample project used to take like 200ms for updates, but now it seems like its sub 50ms (if not less). Really almost feels instant (i know its a tiny project) but even previously on a sample it wasn't this quick. awesome job compose team!

This message was deleted.

Hi guys I am learning side-effect in my project. I want to know when should I use

LaunchedEffect

and

SideEffect

in which scenario. I am adding some piece of code using both effect. Please lemme know if I am doing wrong here.

Has anyone successfully used

@Preview

annotations to generate screenshots for the play store? This was a #showerthought but its been a few hours and I havent been able to pick it apart yet. Seems like an easy approach, as compared to generating all that fake data. Any cons, besides it being very tied to compose (which I dont mind ❤️)?

Is there a plan (even a distant one) to support accessibility settings in Compose

@Preview

? (font size, display scale) Thanks

Hi! I've noticed that

Modifier.progressSemantics

causes recompositions. I've a custom

ProgressIndicator

, and if I use

Modifier.progressSemantics

Android Studio "Layout inspector" shows thousand recompositions. Is it a bug of "Layout inspector", or it is normal?

Hello! I'm surprised, i noticed a bit late that longClicks are not working with non-touch events :( Does anyone has a workaround to get longClick working with tv remotes or gamepad controllers (based on KeyEvents) ?

Hey guys, i need help. I released my new app one week ago. A few days after release, i got multiple issues reporting the same problem. The "comma" is not clickable on the Keyboard on Samsung phones located in germany. I checked the KeyboardType, but i used KeyboardType.Decimal. I will attach a screenshot. System is set to English (Germany). Reproducable with most Samsung phones. Compose Version 1.2.0 Same behaviour with Compose 1.3.0-beta03 There are some known problems on Stackoverflow, but noone has a workaround for compose... https://stackoverflow.com/questions/65184373/comma-doesnt-work-on-samsung-android-keyboard https://stackoverflow.com/questions/72044124/show-comma-instead-of-dot-keyboard

Comma and Dot may be a Language setting specific problem related to the relevant language. It may be interesting to dig into the Compose code to see how the language settings are applied.

This message was deleted.

Hello everyone, I have a question in compose is it possible to create something like this (image in the thread), in xml it is a layerList in compose how could I do it

Why cant I define custom colors in Jetpack Compose?

Button(
    onClick = { /*TODO*/ },
    colors = ButtonDefaults.buttonColors(backgroundColor = Color(0xF7B500))){
}

Is showing me a Grey button but it should be Yellow/Gold

Hey everyone, we use Appium for automation tests, in the past, we used id for testing, what is the equivalent in compose?

Is there a way to properly clip an

AnimatedVisibility

? Clipping passed to the

AnimatedVisibility

modifier is not working and the animation runs with a square

.clip(CircleShape)

so I have two composables that I would like to add to the screen, a TopAppBar that stays at the top, and under it another element if I add them sequentially one after the other (without specifying a column for them to sit in), the top bar appears at the top, and the header appears in the center if I specify a colum, the top bar still appears at the top but now the header stops appearing

Column {
    TopAppBarSearch(
        searchText = searchState.searchText,
        placeholderText = stringResource(id = R.string.search_for_a_city),
        showClearButton = searchState.showClearButton,
        showProgressBar = searchState.showProgressBar,
        matchesFound = searchState.cities.isNotEmpty(),
        onSearchTextChanged = { viewModel.onSearchTextChanged(it) },
        onClearClick = { viewModel.onClearClick() },
        onNavigateBack = { navigateBack() },
        onEmptySearchResults = { NoSearchResults() },
        onSearchResults = {
            Cities(cities = searchState.cities) { city ->
                viewModel.selectLocation(city)
                navigateBack()
            }
        }
    )

    AnimatedVisibility(
        visible = !searchState.isNetworkError
                && !searchState.isOtherError
                && searchState.cities.isEmpty(),
        enter = fadeIn(),
        exit = fadeOut()
    ) {
            MyLocationHeader {
                viewModel.selectCurrentLocation()
            }
    }
}

Anyone experiences issue when using

@Preview

with

rememberAsyncImagePainter

inside it, and showing an error instead?

stacktrace in 🧵

Try setting

width = Dimension.fillToConstraints

to the yellow text

Hi everyone :android-wave: We’re trying to get more input from you all on the way you use the Accompanist Pager for Compose :) Would you be so kind 🌻 to answer any of the following: - What are some of the most important API features that you found in the Accompanist Pager and some you didn’t find so useful? - Are most cases covering single full-page paging with tabs or not? - Have you been using Lazy lists in any way as a replacement, and if so, how? - Related to the above, have you been using Lazy lists to potentially build smaller pages (like carrousels) and was that sufficient? Any feedback is much appreciated, thanks a lot! 🤙

I’m having an issue with loading images via Coil

AsyncImage

where

data

is a

File

, after upgrading to Android 13 (the issue does not repro on Android 12). These images don’t load anymore. Images which load from URI strings still load correctly. Anyone encountered something like this? Thanks in advance. Tested Coil v 2.2.0 and 2.2.1

Hello, how can I use

rememberSaveable

for

Animatable

?

val pathPortion = rememberSaveable { Animatable(initialValue = 0f) }

Compose Version 1.3.0-beta03 released yesterday. Some interesting things from my point of view • Add options to customize line breaking in Text. (I86907) HELL YEAH • `BringIntoViewResponder`s are now able to get the most up-to-date bounds of a request while processing it. (not sure what this is but seems helpful) • Introduce support for spacings between items to experimental

Staggered Grid

(I10b82) • Introduce content padding to experimental

Staggered Grid

(I342ea) • Added

Modifier.withConsumedWindowInsets()

to get consumed

WindowInsets

for use outside

windowInsetsPadding

. • Added

MutableWindowInsets

to allow easily changing

WindowInsets

without recomposition. • Fix fling animation cancellation issue (i wonder if this fixes flinging bottom sheet modals getting stuck when fully open) • Add a Pull-To-Refresh component to Compose (I29168) OOOH What is this!? Another thing from accompanist that can die? (commit message: Migrates Accompanist's SwipeToRefresh to Compose with major changes.) so yes. it can die it seems. • Behavior Breaking Changes (next two points) • The parameter to

remember

and

rememberCoroutineScope

where changed to be

crossinline

. This will report an error for early returns instead of allowing an early return which will cause a later internal error to be reported. • This change can potentially lead to new compiler errors to be reported requiring non-local returns to be removed from the lambdas passed to these functions. (Ibea62) • AndroidX Activity's

BackHandler

API now works within a

Dialog

composable. (I35342) OH YEAH M3: •

ExposedDropdownMenuDefaults

now exposes a padding value for menu items. (I34ee1) ⚠️ Looks like coil and latest compose don't play well together. https://github.com/coil-kt/coil/issues/1473

Hello everyone, I'm using

TextField

with some

annotations

in the

TextFieldValue

, but in the

onValueChange

callback all the

annotations

are gone. How can I restore them?

Hello folks, I'm working with a constraint layout where I'm using a guideline but I can't scroll down even though I have added the vertical scroll; if I remove the guide line everything is working fine as expected. Can anyone help me out?