Hi, I'm learning how effect works and trying to understand why

millis

value doesn't change when I add a log at A - before Canvas. Without the log or when I add log at B instead,

millis

gets updated. Is this an expected behavior?

@Composable
fun DrawSomething(
    modifier: Modifier,
    strokeWidth: Float = 8f
) {
    val millis = animationTimeMillis()

// A: when adding a Log here, millis.value will stop at 0 and won't draw arc
// Log.d("DrawSomething", "millis : ${millis.value}")

    Canvas(modifier = modifier) {

        // B
        // Log.d("DrawSomething", "millis : ${millis.value}")

        drawArc(
            color = Color.Green,
            startAngle = 0f,
            sweepAngle = 0f + (millis.value / 360),
            useCenter = false,
            size = Size(100f, 100f),
            style = Stroke(width = strokeWidth)
        )
    }
}
@Composable
fun animationTimeMillis(): State<Long> {
    val millisState = mutableStateOf(0L)
    val lifecycleOwner = AmbientLifecycleOwner.current
    LaunchedEffect(Unit) {
        val startTime = withFrameMillis { it }
        lifecycleOwner.whenStarted {
            while (true) {
                withFrameMillis { frameTime ->
                    millisState.value = frameTime - startTime
                }
            }
        }
    }
    return millisState
}

I'd like to use BottomNavigation where each tab remembers its navigation state. Is this supported with Compose Navigation?

Anyone ever have this issue with bouncing text in a

TextField

? I can resolve it with

singleLine = true

, but it still chops off the bottom of the sub-baseline letters. This is in a

TopAppBar

in a Scaffold. Thought this might be due to a size constraint on

TopAppBar

? Or maybe just the

topAppBar

content parameter in

Scaffold

? Not sure if there's any weird trickiness with

TextField

itself.

Has anyone worked on a camera or photo gallery? Looking for photo capture / image selector.

How can I get

BottomAppBar

to hide when I scroll down in my

ScrollableColumn

?

Today I tried Jetpack Compose. While it looks promising, has anyone noticed how long it is to update a composable

@Preview

? It takes almost a minute to render each change, and I'm using a decent laptop. Also, is it required to rebuild project to update preview ?

Is someone aware of a sample app where data is not only retrieved but also send to repository? I'm wondering how to collect all the state in different composable when event is triggered. First thought is to hoist all the state to

ViewModel

...

When Scaffold bodyContent includes LazyColumn ,sliding becomes very jerky ！😫

I have this code and I'm getting this weird bug you can see in the video. The bug goes away when I remove the three `Text`s for R, G and B values. Here is the code:

val colors = remember {
    mutableStateListOf(
        mutableStateListOf(Color.Magenta, Color.Blue, Color.Yellow)
    )
}
val activeRowIndex = remember { mutableStateOf(0) }
val activeColumnIndex = remember { mutableStateOf(0) }

...

Sliders(
    colors[activeRowIndex.value][activeColumnIndex.value],
    onColorChange = { colors[activeRowIndex.value][activeColumnIndex.value] = it }
)

@Composable
fun Sliders(color: Color, onColorChange: (Color) -> Unit) {
    Column {
        Row(verticalAlignment = Alignment.CenterVertically) {
            Text(text = "R - ${color.red * 255}")
            Slider(
                value = color.red,
                onValueChange = { onColorChange(color.copy(red = it)) }
            )
        }
        Row(verticalAlignment = Alignment.CenterVertically) {
            Text(text = "G - ${color.green * 255}")
            Slider(
                value = color.green,
                onValueChange = { onColorChange(color.copy(green = it)) }
            )
        }
        Row(verticalAlignment = Alignment.CenterVertically) {
            Text(text = "B - ${color.blue * 255}")
            Slider(
                value = color.blue,
                onValueChange = { onColorChange(color.copy(blue = it)) }
            )
        }
    }
}

https://jakewharton.com/a-jetpack-compose-by-any-other-name/ Anyone else here think there should be some sort of name change? 👍 or 👎 Personally, I've talked to people about Jetpack Compose and they find "Jetpack" to be weird. I think I'm only "okay" with it because I've grown used to "jetpack" as a term that we use when talking about android dev. "Jetbrains Compose" for desktop could also be confusing. I think just having Compose (and saying that its available for Android and desktop) is easiest when talking about the UI, and the compiler and runtime could probably just be renamed. Seems like that would be the least amount of friction.

Hi, we are on the verge of releasing our Android app that is built entirely in Compose 🥳🥳🥳 problem is we have a major blocker:

BasicTextField

often doesn’t bring up the keyboard when focused! When it malfunctions, the cursor is literally blinking, yet somehow the keyboard is not open. This happens on physical Pixel 4a in a release build that is deployed to the play store! Since we are chat-based communities, this is critical. How is it even possible to get into this state, and are there any workarounds/hacks that can fix this reliability bug?

I need to detect touch events and change some state with respect to up and down motion events. The next code (see the thread) works well with simple taps, but if I tap with 3 fingers, it adds only "Down" event, but no "Up". What could be the problem? Do I need to use something else besides

pointerInteropFilter

?

Hi, new to Compose and played around with the Compose codelab samples regarding theming, but having issues with previewing light & dark themes. Greatly appreciate any help / advice!

The Compose's NavigationController doesn't allow for "free-form" navigation. I get that having a laid out static navigation graph is great, but in a considerably large project I don't think its tenable. I was able to create a "hacky" solution. However I'm curious why "free-form" navigation isn't directly supported? Answer: A static graph must to be created at start up to handle resuming after process death Hopefully something better will come along soon!

Hi,  Quick question, is there some quick way to achieve foldable text section like I have on screen? Everything works correctly I just need to have the more after the … so it looks something like this

Are there plans for more spans for

AnnotatedString

? Like

BulletSpan

,

QuoteSpan

, etc. (Unless this can be achieved already?)

Let’s say I’d like to animate a Card() using a FloatPropKey with values from 0f to 1f. How could I approach this currently?

How to combine different gesture detectors using

pointerInput

? My goal is combine zooming (1), scrolling (2) and drag-n-drop (3) on the same composable. 1 and 2 are available with

detectMultitouchGestures

. 3 could be done using

detectTapGestures

+

detectDragGestures

I guess. The idea is to listen to gesture trigger first and then give full control to corresponding gesture routine. Honestly I don’t how to approach this, the examples don’t cover this it seems

Hey, SwiftUI developer, taking the Ray Wenderlich Jetpack Compose course.

Hi, is this documentation up to date? I can't seem to pass a string to the

navController.navigate()

method

How to add animation in the end of the list when using:

LazyColumn

?

Right now there is no possibility to use Transitions when using Jetpack Navigation?

hrm ... with Navigation, is this the proper way to deal with an argument that is an Enum value? I have a sealed class with my routes:

sealed class Screen(val route: String, val title: String, val isTopLevel: Boolean = false) {

    object Category: Screen("category/{postType}", "Category") {
        // here I define a NavType.EnumType for my enum that is used for an argument.
        val postTypeArgType = NavType.EnumType(PostType::class.java)
        
        fun buildRoute(postType: PostType): String {
            return "category/${postType.name}"
        }
    }

    // ... more screen routes defined here..
}

Then I use the Category to build the composable() in the NavGraph Builder. And I use the

postTypeArgType

which is a

NavType.EnumType

from the Category object above to get the postType argument. Is this the right approach?

composable(Screen.Category.route,
        arguments = listOf(
            navArgument("postType") { type = Screen.Category.postTypeArgType },                            
            navArgument("title") { type = NavType.StringType }
        )
    ) { backStackEntry ->
        val vm: CategoryScreenViewModel = navViewModel()

        // Is this the right way to get the `postType` argument from the backstack entry?
        val postType = Screen.Category.postTypeArgType.get(backStackEntry.arguments?: Bundle(), "postType") ?: PostType.OTHER

        CategoryScreen(vm, postType)
    }

Are you not able to use

remember

with an inlined Compose function?

@Composable
inline fun test() {
    val i by remember { mutableStateOf(3) }
}

This method produces a nasty compiler error Part of the error message:

Caused by: java.lang.RuntimeException: Exception while generating code for:
FUN name:test visibility:public modality:FINAL <> () returnType:kotlin.Unit [inline]
  annotations:
    Composable
  BLOCK_BODY
    VAR name:$i$f$test type:<http://kotlin.Int|kotlin.Int> [val]
      CONST Int type=<http://kotlin.Int|kotlin.Int> value=0
    VAR name:i type:<http://kotlin.Int|kotlin.Int> [val]
      CALL 'public final fun remember <T> (calculation: @[ComposableContract(restartable = <null>, readonly = <null>, tracked = <null>, preventCapture = 'true')] kotlin.Function0<T of androidx.compose.runtime.RememberKt.remember>): T of androidx.compose.runtime.RememberKt.remember [inline] declared in androidx.compose.runtime.RememberKt' type=<http://kotlin.Int|kotlin.Int> origin=null
        <T>: <http://kotlin.Int|kotlin.Int>
        calculation: BLOCK type=kotlin.Function0<kotlin.Int> origin=LAMBDA
          COMPOSITE type=kotlin.Unit origin=null
          FUNCTION_REFERENCE 'private final fun test$lambda-0 (): <http://kotlin.Int|kotlin.Int> declared in dev.birdsofparadise.mua.lifecycle.ComposeActivityKt' type=kotlin.Function0<kotlin.Int> origin=LAMBDA reflectionTarget=null

Hey! I'm starting to play with compose and I have a question around

SavedStateRegistry

. I notice I have an

Ambient

for

UiSavedStateRegistry

but there's no for

SavedStateRegistry

. - and look like they are totally different types so I can't create a custom

AbstractSavedStateViewModelProviderFactory

without a

SavedStateRegistryOwner

. What is the correct way to get a

SavedStateRegistryOwner

in a composable? 🤔

How can I disable the ripple effect when using card in Compose?

When I shrink a Card using a tween animation, how can change the size another card as soon as the tween animation is finished? Traditionally, I’d think of an end-Listener and start an animation on another View

Hi. Is there a way to render out of parent bounds I need to transform topappbar to searchscreen

Is the title not centred is normal.