Hi. I am trying to get this layout

Question to compose developers (similar question like question about paddings in

TextField

🙂 ) Why don’t you left any possibility to change

strokeCap

for

CircularProgressIndicator

? I can change

strokeWidth

[thread], but somewhy i cannot change cap

New SplashScreen lib + Compose = bug? Or I do something wrong?

Is there a way to connect LocalProvider with the Kotlin FLow? I am trying to change dynamically the LocalProvider with DataStore flow.

I have a question about jetpack compose UI testing. I use side effect (LaunchedEffect) in root of my Composition. Actually this side effect subscribes on flow (just

Boolean?

) to post new root in NavHostController. I use it to unauthorize user (when error 401 received from server, for example) or authorize user when it enter credentials. In app code it works perfect. But when i go through app with compose UI tests i am getting exception when user just authorized. Something like

You can perform this action (post new root in NavController) only in main thread

. When i dive into

LaunchedEffect

i found that it uses coroutines context from current composer [thread]. But for ui tests this current composer returns

TestCoroutinesContext

that use

Dispatchers.Default

instead of

Dispatchers.Main

. It leads that side effects crashes the app, if trying to access UI thread operations. How must i to act in this situations? Use somehow MainDispatcher directly in code (it is far from obvious)? Looks like there will be good approach to add to user the possibility to change composer dispatcher for UI tests

Hi, is this behavior intended in Material? Why is it inconsistent?

MaterialTheme {
    CompositionLocalProvider(
        LocalContentAlpha provides ContentAlpha.high
    ) {
        Surface(color = MaterialTheme.colors.primary) {
            LocalContentAlpha.current // 0.87 (LowContrastAlpha)
            ContentAlpha.high // 1.0 (HighContrastAlpha)
        }
    }
}

I have a basic question about screenshotting composables. AFAIK, there are 2 main ways that one can go about this; • AndroidView->ComposeView wrapping and draw ComposeView onto a canvas • PixelCopy and directly read from window The second method is useless when composable content is bigger than the window. Any overflowing content would be lost. The first method does not have obvious blockers for getting the job done but I found a small problem. If the composable uses graphicsLayer in any way, it isn't reflected when

composeView.draw(canvas)

is called. All graphicsLayer modifications like

offset

,

scale

,

rotation

are disregarded. So my question is; is there a way to enable graphicsLayer while drawing a

View

onto a Canvas?

Where is translationZ in Compose? I want to animate it, but graphicsLayer has only

shadowElevation

(only for shadows),

translationX

,

translationY

Discussion time! For those going pure compose... Are you using Compose navigation arch component or something else? And why not just use the arch component?

Has anybody tried

navigation-compose 2.4.0-alpha05

? There must have been some behavior changes because my navigation logic now leads to infinite loops which didn’t happen with alpha04.

Question on converting flow to liveData. I have a class which I am using as a ViewModel (not android viewModel) which contains a flow. I get excessive collection if I pass this viewModel into the Composable view and observe the flow. I notice that if I convert to liveData in the view model instead that the excessive emission doesn't occur. Am I missing something on how this should be done?

class MyViewModel(model: Model) {
    val userLoggedInFlow = model.usernameFlow.map { it != null } // returnes if there is a username
}

@Composable
fun myView(viewModel: MyViewModel){
    val state = viewModel.userLoggedInFlow.asLiveData().observeAsState()
    
    if(state.value != null){
        //Show stuff here
    }
    else {
        //navigate to the login screen
    }
}

Hi. Is there a way to calculate if a text (on

Text

) is going to take more than a single line?

I am currently writing a Splash Screen for an app, and I want to use this time to make a REST API call to our server that will check if the app is too outdated to properly access the API. I am currently using the single-activity model with a single Compose NavHost. I was wondering when the best time would be to trigger the viewModel to start the call. Should I trigger it when the viewModel is constructed, can the NavHost trigger the viewModel when I navigate to splash, or should I trigger this in some other way? I set up the SplashViewModel to call navigate on the navController to go to the next screen if it gets a valid response from the server.

Hey guys, i try Jetpack Compose for my projet and i get a render problem when i want to preview a composable, do you have any solution to resolve this issue. Gradle Bluid: My Code:

class MainActivity : ComponentActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        setContent {
                // A surface container using the 'background' color from the theme
                Surface(color = MaterialTheme.colors.background) {
                    Greeting("Android")
                }
        }
    }
}

@Composable
fun Greeting(name: String) {
    Text(text = "Hello $name!")
}

@Preview(showBackground = true,name="Text Preview")
@Composable
fun DefaultPreview() {

        Greeting("Android")
}

Message of the error : Attach Msg Error.txt :/

Hi. I should note that I started to notice a growing number of questions about how to turn Compose widget into a bitmap(in the manner

View#drawingCache

we had with legacy

View

system). And I didn't understand why, until now. Now I am going to raise this issue too. 😄 What I'm interested in: (see attached images 🧵) The question: Is it possible to capture the underlying layers behind the widget in order to manipulate the pixels later? Note: It is not always possible to wrap every set of composable widgets in an AndroidView and use the rendering cache in the "old" way. Is it planned to provide such functionallity with future versions of Compose(

1.1

,

1.2

,...)? And is it technically possible at all with Compose? Thanks.

Hey, is there a way to get rid of font padding within a Text element in jetpack compose? I have a Button and the text within it is slightly off center, which I assume is due to font padding. Is there an equivalent to includeFontPadding=false?

How do I get the size of a composable AFTER it's been laid out and measured? i.e. I want to know that my image is laid out on the screen at a final resolution of 200px x 400px.

hello, I’ve noticed running Compose apps in

Android Studio Bumblebee | 2021.1.1 Canary 3

, requires uninstalling and installing app so updates got reflected on the testing device. clicking instant run doesn’t always reflect all the changes which make it harder to debug.

Hey has anyone seen interesting behaviour where lazy lists (in our case lazy columns) recompose most of the visible items without the data changing? We are observing a calc based on the first index / first item offset to hide /show something which doesn’t look like its in the same compose scope as the list. When this value becomes stable it stops this recomposing behaviour. Theories in thread.

Hey. I want to call a ViewModel function only ONCE in a composable. e.g. viewModel.getMovies() It should not be called on re-composition. How do I achieve this?

Hi. After upgrading to

navigation-compose:2.4.0-alpha05

my view model

init {}

is called continuously. Does anyone having the same issue? I’m using

hilt-navigation-compose:1.0.0-alpha03

Is it possible to snap an animation,

Animatable

or

updateTransition

, during the same composition? When I update the state or call

snapTo

, the update happens in the next frame or so.

Is anyone facing a crash at app startup after updating to

Android Studio Bumblebee | 2021.1.1 Canary 4

LOGS in 🧵

Getting this error when I upgrade to navigation-compose 2.4.0-alpha05

java.lang.ClassCastException: androidx.navigation.NavGraph cannot be cast to androidx.navigation.compose.ComposeNavigator$Destination

This happens when I try to navigate

navController.navigate(Screen.Authentication.route) {
    popUpTo(Screen.Main.route) {
        inclusive = true
    }
    launchSingleTop = true
}

Worked fine with 04

I've posted a Compose puzzler on Twitter about multiple

Modifier.border()

that overdraw each other (link and code in the thread). Gave an explanation why it's this way, but after I read it again I'm unsure if it's correct and I have second thoughts. Can someone shed some light into the topic?

Hi. In

LazyRow

when I call

animateScrollToItem

back to a short item seems like it doesn’t animate the scroll at all. Sample code in 🧵

Want to create typical code input like at . What is the best option in compose to do the same? I should request user input somehow. Few years ago i did same with invisible EditText, that request focus and user input on screen start and on screen click. But it is impossible in compose.

Is there some guideline for compose code formatting already?