Hi 🙂 With compose navigation bottom bar, how can I get the usual behaviour of scrolling to top when tapping the icon of the screen i'm already on ?

How to use

Divider

as vertical line?

From the Thinking in Compose video How would you manage all the click events with single

content: @Composable () -> Unit

lambda? How would somebody handle the click events inside the lambda?

Is there a way to detect preview mode?

Hi all, is there a way to apply different 'lineHeight' to a specific region of the text inside [Text] composable?

Can I create

viewModel

scoped to a

composable

using

navigation-compose

?

https://android.googlesource.com/platform/frameworks/support/+/refs/heads/androidx-master-dev/compose/ui/ui-graphics/src/commonMain/kotlin/androidx/compose/ui/graphics/Brush.kt#279 is marked as internal, which means that to create a multistop linear gradient (not just an array of colors, but also an array of stops) requires to use the

ShaderBrush

+

LinearGradientShader

. Is that intentional?

If I create viewModel inside a composable then I can’t preview the composable. Also, it is recommended to create a composable which is independent of the Navigation Library. And to test UI easily it is recommended to create stateless composable. To solve all of these I am thinking about the following pattern: 1. Every screen composable will have three parameters. (a) state: a data class. (b) viewModelCallback: an interface so that the screen can interact with the viewModel. (c) screenCallback: an interface to interact with navigation and activity results 2. There would be an overloaded version of the screen which will be stateful and will know about navController and viewModel. 3. I will use a stateless screen composable to preview and test. What do you think about this approach? for every screen, I have to create a data class, two interfaces, two dummy implementation of those for preview, and test implementation for those. will these extra works be beneficial or I am over-engineering

Ok I have two more questions. 1. Since no one was able to point me to the right direction so far: are there any samples of providing different layouts depending if a user is having a big screen or a small screen (e.g. tablet I want side by side and on phone I want two panels below each other) 2. Is there any documentation for all the Material (and non material components)? For some reason I can't find the KotlinDoc for that?

hi all, i'm trying to interop with an android view inside of compose, specifically this library Konfetti. It's not filling the screen, nor is the animation playing - this is what i have so far:

@Composable
fun Confetti() {
    val context = ContextAmbient.current
    val konfettiView = remember {
        KonfettiView(context).apply {
            build()
                .addColors(Color.YELLOW, Color.GREEN, Color.MAGENTA)
                .setDirection(0.0, 359.0)
                .setSpeed(1f, 5f)
                .setFadeOutEnabled(true)
                .setTimeToLive(2000L)
                .addShapes(Square, Circle)
                .addSizes(Size(12))
                .setPosition(-50f, 500 + 50f, -50f, -50f)
                .streamFor(300, 5000L)
        }
    }
    
    AndroidView({ konfettiView }, modifier = Modifier.fillMaxSize()) { view ->
        // Do something here?
    }
}

really hard to understand what's going wrong here! any advice?

Since Compose Navigation added NavOptions in alpha02, I'm trying to use it but I dont understand how can I specify a popUpTo destination as it requires an Id(Int) and we only have route(string) in the Compose navigation graph. Thanks for your help guys!

Did something change in alpha07 for ViewModel and hilt usage? In an

AndroidEntrypoint

annotated activity, I'm now getting

has no zero argument constructor

when using the

viewModel()

composable to retrieve an instance (the ViewModel's constructor does have the

ViewModelInject

annotation)

How can I get the current orientation of the device in a composable?

E/AndroidRuntime: FATAL EXCEPTION: main
    Process: com.redrield.androidds, PID: 15301
    java.lang.NoSuchFieldError: No field Companion of type Landroidx/compose/runtime/SlotTable$Companion; in class Landroidx/compose/runtime/SlotTable; or its superclasses (declaration of 'androidx.compose.runtime.SlotTable' appears in /data/app/~~58hYPPzhGRjb56GwSeeO0g==/com.redrield.androidds-WjdLhG2Oom4gM1SnqQGjqg==/base.apk)
        at androidx.compose.material.MaterialThemeKt.MaterialTheme(MaterialTheme.kt:112)

Any idea why this would be happening? It started after I added compose-navigation, even if I've cut out all reference to it where the theme composable is being called, in fact there's no content there at all

implementation 'androidx.compose.ui:ui:1.0.0-alpha07'
    // Tooling support (Previews, etc.)
    implementation 'androidx.ui:ui-tooling:1.0.0-alpha06'
    // Foundation (Border, Background, Box, Image, Scroll, shapes, animations, etc.)
    implementation 'androidx.compose.foundation:foundation:1.0.0-alpha06'
    // Material Design
    implementation 'androidx.compose.material:material:1.0.0-alpha06'
    // Material design icons
    implementation 'androidx.compose.material:material-icons-core:1.0.0-alpha06'
    implementation 'androidx.compose.material:material-icons-extended:1.0.0-alpha06'
    // Integration with observables
    implementation 'androidx.compose.runtime:runtime-livedata:1.0.0-alpha06'
    implementation "androidx.navigation:navigation-compose:1.0.0-alpha02"

compiler extension version 1.0.0-alpha06

In Jetchat, when the Selector is Expanded, if I put app in the background and reopen it, keyboard is also shown. Is this expected behaviour?

Anyone made a color wheel with compose? I'd love to check it out

Hello, what is the equivalent of fitSystemWindows in Jetpack Compose ?

How can I make a sweep gradient?

Hello, does anyone know why the compose canvas does not have a function to draw text similar to the native canvas? Is it not implemented yet or we should just use the

drawContext.canvas.nativeCanvas()

?

Hey, what's the best way to set the children of a row to a certain width based on percentage rather than a concrete value? Or is it best to calculate the concrete value?

Are returns inside composable currently bugged (alpha07)? I'm getting a lot of

java.lang.IllegalStateException: Start/end imbalance

when using them Wrapping the whole follow code into a conditional block instead fixes the issue

Have anyone tried nested navigation? When I make the nested navigation the startDestination then it works otherwise I can’t go to the nested navigation. How can I navigate to the nested navigation?

ShohayTheme {
                val navController = rememberNavController()

                NavHost(navController = navController, startDestination = Route.Splash) {
                    composable(Route.Splash) {
                        val splashViewModel = hiltViewModel<SplashViewModel>()
                        SplashScreen(
                            viewModel = splashViewModel,
                            navigateToAuth = { navController.navigate(Route.Auth) },
                            navigateToHome = { navController.navigate(Route.Main) }
                        )
                    }

                    navigation(startDestination = Route.NestedAuth.Social, route = Route.Auth){
                        composable(Route.NestedAuth.Social) {
                            Text(text = "Social Flow")
                        }
                    }

                    composable(Route.Main) {
                        Text(text = "Main Flow")
                    }
                }

            }

Seems like using paging compose

items

with

LazyColumn

does not restore the scroll position when navigate back using navigation compose. Does anyone have the same issue?

After updating to

alpha07

& chrisbanes/accompanist v0.3.3.1 , loading a

CoilImage

in this manner:

CoilImage(
    contentScale = ContentScale.Crop,
    data = "some image url",
    fadeIn = true,
    error = { Text("Could not load image") }
)

fails with:

skia: --- Failed to create image decoder with message 'unimplemented'

The result is that the image does not load, and the error Composable is shown. Anyone else experiencing this?

Hi. I have a LiveData<List<Items> that Observe it inside composable like:

val items = viewModel.liveDataItems.observeAsState(initial = emptyList())

After user do some action I wanna expand that specific item. For do that I will tell viewModel update expandation field of selected item. Then I will update liveDataItems and want to expandations happens. I have two problem here, first making change to list items not trigger Live Data in compose so I have to replace all data with new that specific items is updated with isExpanded=true. Second issue is with tis way I will lose my scroll point and view will render from start. How I can handle expandation like this to have

What can be this composable, it has fixed height, not expandable (adding task in Google Tasks App)? I have used BottomDrawerLayout , but it doesnt let fix height , any idea? 🤔 Is it something similar to Crane app?

Hi all, I'm using

EditText

view with

AndroidView

composable, when I press back button with

EditText

in active state,

KeyInputModifier

is crashing with

"KeyEvent can't be processed because this key input node is not active."

Is there any information on what i'm doing wrong and how to fix this? After a briefly looking into compose source code I was not able to find any handle to prevent this crash, so I'm just suppressing the crash on activity level inside of

dispatchKeyEvent

method, is there a better workaround for the issue? (compose 1.0.0-alpha07)

Is there a way to parse a string to Color in Compose? 🤔