Not quite yet

Hi, Does anyone know how I can disable Split mode which is the default option, to Code only in Android Studio?

Is there a pattern for use by libraries of composables, so the library knows how to create composables from the app's design system? I am not worried about simple parent-child relationships, where we can get away with a

content

composable lambda. I am more worried about cases where the library itself should be calling composable functions for certain roles, but it has no a priori way of knowing what those functions are. For example, if a library wants to render a button, it needs some composable for that. But

Button()

is a Compose Material thing, and the argument made here on several occasions is that Compose Material is just one possible design system. Somehow, the library needs a way to know "this is how I build a button", in such a way that it uses the app's chosen design system. Do we have a pattern for doing this? For apps themselves, they can simply use the right composable functions, but published libraries do not have that option, as they will be used by many apps. My fear is that, in the absence of such a pattern, libraries will tend towards "you can have any design system you want, so long as it is Compose Material".

When I add this to my project

buildFeatures {
        compose = true
    }

I get the following error:

com.intellij.openapi.externalSystem.model.ExternalSystemException: Could not create task ':app:compileDebugKotlin'.
org/jetbrains/kotlin/gradle/tasks/KotlinCompile

Any ideas why? Im trying to use compose alpha 10 on the latest canary AS and kotlin 1.4.21

The behavior of

Popup

has changed in alpha11. Width is now limited to parent width. Is this intended?

Hi @Doris Liu, I was reading around Transition Samples and found this:

@Composable
fun PoppingInCard() {
    // Creates a transition state with an initial state where visible = false
    val visibleState = remember { MutableTransitionState(false) }
    // Sets the target state of the transition state to true. As it's different than the initial
    // state, a transition from not visible to visible will be triggered.
    visibleState.targetState = true
    ...
}

I was wondering whether doing:

visibleState.targetState = true

is fine? Like to create an "Intro Animation"? or is it better to put that inside a

SideEffect

? or is there a better way?

Is there any update on supporting transitions in compose-navigation

In alpha-09 and compose paging alpha-05, I was collecting like in the code snippet below:

val paginatedBlockedUsers = settingsViewModel.fetchBlockedUsers().collectAsLazyPagingItems()
 LazyColumn {
    itemsIndexed(paginatedBlockedUsers) { index, item ->
        if (item != null) {
            UserListItem(
                item = item
            )
        }
    }

After upgrading from Alpha 9 to Alpha 11 when paging is on alpha-05, I get following error:

one of the following functions can be called with the arguments supplied:
public inline fun <T> LazyListScope.itemsIndexed(items: Array<TypeVariable(T)>, crossinline itemContent: LazyItemScope.(index: Int, item: TypeVariable(T)) -> Unit): Unit defined in androidx.compose.foundation.lazy
public inline fun <T> LazyListScope.itemsIndexed(items: List<TypeVariable(T)>, crossinline itemContent: LazyItemScope.(index: Int, item: TypeVariable(T)) -> Unit): Unit defined in androidx.compose.foundation.lazy

How do I use .collectAsLazyPagingItems() and itemsIndexed(paginatedItem) { index, item -> } in alpha 11 ?

I'm getting a crash when doing this:

val items = viewModel.items.collectAsState(initial = listOf())
LazyColumn {
    items(items.value.size) { index ->
        ...
    }
}

But if I do

val items = viewModel.items.collectAsState(..).value

and

items(items.size)

, it works fine. Why doesn't the first snippet work?

Hi, does LazyGrid have span strategy. I' ve asked a question at Stackoverflow: https://stackoverflow.com/questions/65981114/does-jetpack-composes-lazyverticalgrid-have-span-strategy We can change grid count dynamically, but I want to have a full width footer when loading happens. Is there a way I can set span count for specific item?

Is anyone running Instrumented Tests against Compose Layouts... or doing so in Firebase Test Lab?

Hi, If someone could take a look at my problem, i’d be grateful https://stackoverflow.com/questions/65993932/dynamic-row-width-compose Cannot get row with basic text field to “shrink” properly and add another element to the right side

Hi all ! I'm trying to update my Jetpack Compose project, but I still get this error

Execution failed for task ':app:checkDebugAarMetadata'.
> Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
   > Could not find androidx.ui:ui-tooling:1.0.0-alpha11.
     Searched in the following locations:
       - <https://dl.google.com/dl/android/maven2/androidx/ui/ui-tooling/1.0.0-alpha11/ui-tooling-1.0.0-alpha11.pom>
       - <https://jcenter.bintray.com/androidx/ui/ui-tooling/1.0.0-alpha11/ui-tooling-1.0.0-alpha11.pom>
     Required by:
         project :app

Possible solution:
 - Declare repository providing the artifact, see the documentation at <https://docs.gradle.org/current/userguide/declaring_repositories.html>

Here my build.gradle

// Top-level build file where you can add configuration options common to all sub-projects/modules.
buildscript {
    ext {
        compose_version = '1.0.0-alpha11'
    }
    ext.kotlin_version = "1.4.21"
    repositories {
        google()
        jcenter()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:7.0.0-alpha05'
        classpath "org.jetbrains.kotlin:kotlin-gradle-plugin:$kotlin_version"

        // NOTE: Do not place your application dependencies here; they belong
        // in the individual module build.gradle files
    }
}

allprojects {
    repositories {
        google()
        jcenter()
    }
}

task clean(type: Delete) {
    delete rootProject.buildDir
}

Here my app build.gradle

plugins {
    id 'com.android.application'
    id 'kotlin-android'
}

android {
    compileSdkVersion 30

    defaultConfig {
        applicationId "com.loloof64.chessexercisesorganizer"
        minSdkVersion 21
        targetSdkVersion 30
        versionCode 1
        versionName "1.0"
        vectorDrawables.useSupportLibrary = true

        testInstrumentationRunner "androidx.test.runner.AndroidJUnitRunner"
    }

    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), '<http://proguard-rules.pro|proguard-rules.pro>'
        }
    }
    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }
    kotlinOptions {
        jvmTarget = '1.8'
        useIR = true
    }
    buildFeatures {
        compose true
    }
    composeOptions {
        kotlinCompilerExtensionVersion compose_version
        kotlinCompilerVersion '1.4.10'
    }
}

dependencies {

    implementation "org.jetbrains.kotlin:kotlin-stdlib:$kotlin_version"
    implementation 'androidx.core:core-ktx:1.3.2'
    implementation 'androidx.appcompat:appcompat:1.2.0'
    implementation 'com.google.android.material:material:1.2.1'
    implementation "androidx.compose.ui:ui:$compose_version"
    implementation "androidx.compose.material:material:$compose_version"
    implementation "androidx.ui:ui-tooling:$compose_version"
    implementation "androidx.compose.material:material-icons-extended:$compose_version"
    def nav_compose_version = "1.0.0-alpha06"
    implementation "androidx.navigation:navigation-compose:$nav_compose_version"
    implementation 'androidx.lifecycle:lifecycle-runtime-ktx:2.3.0-rc01'
    testImplementation 'junit:junit:4.13.1'
    androidTestImplementation 'androidx.test.ext:junit:1.1.2'
    androidTestImplementation 'androidx.test.espresso:espresso-core:3.3.0'
}

I've just downloaded the latest Android Studio canary today

We're using a Crossfade inside a top-level Scaffold to fade between "screens". However, different screens need different TopBar icons and onClickListeners, which we currently set-up inside the screens using onActive(). This would translate to DisposableEffect without a key, which is declared as sign of a bug. Since crossfade renders stuff in weird order, how are we supposed to ensure the set-up code for the topbar is only launched "onActive"? Or in general: aren't there things that are supposed to run once when components become visible? Setting focus is another example. I guess the whole pattern we use may be wrong (setting up the top-bar from within subcomponents), so I'd be happy to hear about other solutions, too.

Is there a simple way to convert the following (from alpha07) ?

Image(asset = vectorResource(id = imageRef), modifier = modifier)

How would I access the current theme settings in a compose application? i.e. Right now I use

MaterialTheme.typography.h1

statically when I want to set an h1, but how would I gain access to the theme that is actually set to get it’s typography, and potentially overridden styles?

In this code (see thread), when a button is pressed, the message "Key() composed ..." prints four times, one for each Key. I wasn't expecting anything to print at all, since Key doesn't read "buttonPressed".

How to undo a click in Compose? Let's say we want to set a variable to A when a UI is clicked and to B when it is released?

I see some performance improvement on LazyColumn when using a big list filled with cards on alpha-11. I personally thank you compose team 👍

Question about the requirement for a

ViewTreeViewModelStoreOwner

to be configured when

AbstractComposeView

is attached: Is that requirement just there to ensure that the

viewModel()

composable function always works, if any code in the composition happens to call it? Or is there actually something in the Compose foundation that’s relying on a

ViewModel

?

Does anyone got to work

@Preview

on

alpha10

? Marking composable with

Preview

gets me

androidx.ui.tooling.preview.PreviewActivity is not an Activity subclass or alias

. Using AS 4.2 Beta 4.

Hi! I built an app using Compose completely. It is sort of a simple game though. My question here is: I have multiple cards and those cards are swiped until the end. At the very end, there is a button to play again. I cannot find any samples on how to draw the cards again on the screen. How can I do that?

Say I have a data class with two properties - one that is declared in primary constructor, one as “normal” property. A

livedata

of said data class was part of state in my view model. I started to observe it as state. What I found out is, I believe, is an optimisation that compose is applying, but correct me if I’m wrong here. When I

postValue

with a new data class, with changed property that is declared in primary constructor,

compose

catches that and triggers recomposition on state - so that’s correct. Now,

postValue

with my data class with a change to a property that was not part of the primary constructor -

compose

does not trigger recomposition, even if observer in

observeAsState

is triggered.

I’ve seen this topic mentioned only once or twice with barely any discussion and I think it could be quite useful debating about this: I believe in compose-only android projects (for UI, ofc) we should handle config changes instead of recreating the activity. And, as a consequence, I also believe we should avoid using the Android ViewModel. Thread with discussion:

Has anyone experienced a

java.lang.NullPointerException: null cannot be cast to non-null type androidx.compose.ui.graphics.AndroidPathEffect

when using a

androidx.compose.ui.graphics.PathEffect

on a

ContentDrawScope.drawCircle

?

Does anyone here use compose in a multimodule project? It seems to work fine in single module but I get the above error in a multimodule setup

This message was deleted.

Why is there a separation between Alignment and Arrangement. It’s a little annoying that I have to import 2 separate types to be able to center the content with a Row or Column.

Is it possible to bind ViewModel with NavHost/NavGraph in Compose only app with zero fragments?

Is there any way to override the fling logic in

ScrollableController

for scrollable modifier? I'm trying to implement something similar to the

PagerSnapHelper

of RecyclerView but found it difficult using

FlingConfig

because I have to know current offset, page size, etc to calculate fling distance and if I implement it using

FloatDecayAnimationSpec

then it can't be stateless.