anyone else seeing this kinds of problems when editing a composable with preview also it takes 60+ seconds to even see a change (even with super simple composables)

Hello everyone! Recently I’ve encountered a problem with kotlin inline functions using compose. Sample code:

// there is any nullable computed condition possible
val test: Boolean? = null
test?.let {
    println("succeed")
} ?: run {
    println("error")
}
test?.let {
    Greeting("Android")
} ?: run {
    Greeting("ios")
}

For kotlinVersion=1.5.31, composeVersion=1.0.5 works as expected (

println("error")

,

Greeting("ios")

are called). For kotlinVersion=1.6.0 (and higher), composeVersion=1.1.0-rc01 composable function after

?:

is never called, even though

println("error")

is called. This behaviour could be easily reproduced for a new project from Android Studio wizard with default compose activity template. Does anyone have the same problem? Any ideas how to fix this for newer kotlin versions without rewriting code for using if-statements?

Is there anyway to render a composable at a lower resolution than the screen? For making pixelated UI. E.g. render it at 360x640 and upscale it (no anti-aliasing) to the screen's native 720x1280 I've tried using Modifier.scale(2f), but I still get native-pixel-sized rendering artifacts.

What can I do to prevent WebView from reloading on screen rotation?

Is it possible to use material3 and material2 together? We have a large project written with material2 components and want to migrate some components to use material3 (such as the collapsing toolbar)

Hello, in the simple row example shown below, when the current timestamp changes value, all the text shifts to the side depending on the current timestamp length. Is there a way to prevent this and just have the artist text be uninfluenced by a change in the current timestamp size?

Row(horizontalArrangement = Arrangement.SpaceBetween, modifier = Modifier.fillMaxWidth()) {
    Text(currentTimeStamp ?: "--")
    Text(artist ?: "")
    Text(endTimeStamp ?: "--")
}

Hi all, when using navigation in compose what is the difference and best practice when passing data as argument, between

navController.currentBackStackEntry?.savedStateHandle?.set("person", person)

and

navController.currentBackStackEntry?.arguments?.putParcelable("person", person)

@Ian Lake what is the difference between these two approaches

data class Person(val name: String)
class PersonViewModel: ViewModel() {
    private val _itemsFlow: MutableStateFlow<List<Person>> = MutableStateFlow(emptyList())
    val itemsFlow: StateFlow<List<Person>> = _itemsFlow

    private val _itemsState: MutableState<List<Person>> = mutableStateOf(emptyList())
    val itemsState: State<List<Person>> = _itemsState
}

@Composable
fun PersonScreen(viewmodel: PersonViewModel = viewModel()) {
    val itemsFromState: List<Person> by viewmodel.itemsState
    val itemsFromFlow: List<Person> by viewmodel.itemsFlow.collectAsState()
}

they are all returning

List<Person>

and recomposed whenever data changes

I have an app that’s using SQLCipher + Room and I want to ask the user for the password again when they return after leaving the app so I close the database. When they leave the single Activity app, in

onStop

, I close the database. When they return, I use the Navigation component to direct them to the Password Screen. The screen with the list of data uses a

ViewModel

that exposes Flow from a Room DAO. The problem I’m having is that observing this from my

ItemList

Composable apparently leaks the DAO (and hence the Database instance) when the user leaves, and when the user unlocks the app again, the

ItemList

is still collection this Flow, which makes the app crash. Using

asLiveData

on the

Flow

fixes the issue. Am I doing something wrong by observing the Room

Flow

from a

Composable

like this or is this some weird bug?

Is there a way to convert compose

Painter

to a

Drawable

? I know that for the other way there is

painterResource()

and

rememberDrawablePainter()

in Accompanist, but I have not found anything about the inverse way.

Should Scaffold be used in every screen (ProfileScreen, HomeScreen, ...) or should it only be used once at the top level with some logic to fit with each screen?

Hi, I want to introduce compose slowly into my app. Its a single activity, multiple fragment app. How best to do this for the next screen i want to develop?

I'm probably missing something basic here. I'm going to blame it on sleep. But this defintiely used to work, but now the IDE is complaining "Parameters must have type annotation"

class LoginUiState(
    var screenTitle by mutableStateOf("")
)

That never worked - are you mixing up

(params)

with

{ ... properties ... }

Are there plans for Compose to support Android 12 scroll effects out of the box, just like it is on Android view system?

This message was deleted.

Is there a good way to hide or prevent the selection dropper icon from displaying in a TextField? More details in thread.

since coroutine scope is used in almost all screens, and to avoid passing it around. does it make sense to provide it via compositionLocal in the theme ?

Hi all, I am hoping to advocate for allowing deep links as start destinations within compose navigation. I saw this thread that discussed this a several months ago, but it doesn't seem to have reached the outcome I expected. I've raised a ticket to introduce this behaviour (https://issuetracker.google.com/issues/214733434), but it was marked as a duplicate of an issue with a similar explanation. I don't suppose anyone else would be interested in discussing this?

Hi. What could be the root cause of

IllegalStateException: LayoutNode should be attached to an owner

(see comments for more info)

Hi there, I'm trying to use 

accompanist-insets

 to adjust my view size according to the height of the keyboard but when the insets finish animating, they reset to 0. Anyone seen this behavior? Any ideas on how I could fix it? I added a green box that displays the value of 

LocalWindowInsets.current.ime.bottom

 to show it is going back to 0 at the end of each animation.

Hey guys, is it possible with accompanist viewpager to only allow swiping right to left?

is it okay to return constant view in AndroidView factory?

val btn = Button(context)
AndroidView(factory = { btn } )

Hi there. I am trying to build an impression tracking SDK. To check if the

Composable

in the viewport, I am using a custom modifier with

onGloballyPositioned

method. Inside the lambda, am comparing the

x and y

cords of the

Composable

and compare it with window height/width. It works, but am wondering if there’s any better method/approach? 🙂

There is an edge-case issue we just ran into while testing our app that is about to be released in the Play Store. When the Switch is swiped by the user the

onCheckedChange

callback is called. We launch a request to our server and if it is successful only then we change the actual value that is backing the Switch’s checked state. If this happens in around 100ms the switch can stuck in an endless loop. Did anyone have a similar problem? It would be nice if we did not have to touch anything below VM layer to prevent this.

LaunchedEffect can see ‘updated’ State objects, but not non-state variables right? That why we use rememberUpdatedState. Can some1 explain this better to me please

Is there a way to have the m3 theme builder generating the tonal palette with a target primaryColor (either dark/light) ? Currently you can only use seed color but that color never ends up in the palette.

I'm trying to have an InputField on the screen, but the input field is just a button that opens up a modal (my designers decision) Any idea why something like this doesn't actually function properly. The onclick is never called and it just leave you to type in the field.

@Composable
fun FakeInputFieldButton(modifier: Modifier, onClick: () -> Unit, valueText: String) {
  val someFunc = {}
  OutlinedTextField("text", {}, modifier.clickable { someFunc() })
}

I think there is an issue with the calculation of the LocalContentAlpha in themes, the LocalContentAlpha is determined before the LocalContentColor is set. This results in wrong contrast values and nested themes use the LocalContentColor from the outer themes. More details in the thread.