Any known issues using reflection with Compose, keep getting this simply just trying to get at a function name

Hey guys. Perhaps less so with Kotlin, but it seems most projects end up having some sort of "utils" file. Here are some I have for Compose. Are these useful? Or do they reflect solutions to anti-patterns elsewhere in my code? What utils do you have that others may find useful?

BottomNavigation(LayoutPadding(bottom = systemInsets.bottom)) {

It seems to me background is drawn within paddings?

from ObservableColorPalette:

This allows for large performance improvements when the theme is being changed, especially if it is being animated.

Animating themes is pretty cool

How can we apply LayoutPadding to all children of either Column or Row?

Is there any place where we can write feedback for the Compose team?

What is an alternative for LayoutFlexible ?

When is proper navigation support expected to come out?

I am getting this error when moving between activities.

java.lang.IllegalStateException: Node should be attached to an owner

It is occuring to me when I upgrade compose version to dev-07.

It seems that Vectors.kt file is redundant in the projects JetNews (dev-07). A navigation button could seen as:

navigationIcon = {
                        IconButton(onClick =  {
                            scaffoldState.drawerState = DrawerState.Opened
                            },
                            children = {
                                        Icon(icon = vectorResource(id = R.drawable.ic_jetnews_logo), tint = Color.White)
                                    }
                                )
//                        VectorImageButton(R.drawable.ic_jetnews_logo) {
//                            scaffoldState.drawerState = DrawerState.Opened
//                        }
                    }

And VectorImage could be replaced to:

Icon(icon = vectorResource(id = R.drawable.ic_bookmarked))
//VectorImage(id = R.drawable.ic_bookmarked)

I've found various cases positional memorization is the "wrong" recompose method, and I actually need a destructive update. Any suggestions better ways to handle this?

It seems like extending interfaces or abstract classes containing @Composable annotations has a regression in dev-06+. I have an use case where I have an interface

interface Foo { val view: @Composable() -> Unit }

with an implementation in a different module, using dev-06 and above fails at compile time with this error:

error: cannot access Foo
public final class FooImpl implements ...Foo {

bad class file: .../classes.jar(.../Foo.class)
undeclared type variable: N

I have been on Canary Channel so I could use Compose, why is AS constantly offering me the beta releases? do they support compose now?

Is there a way to write @Composable functions after async calls?

One thing really nice with Scala 3 is union types. It will be wonderful if Kotlin support it, then we can have a API

fun Button(text: String | AnnotatedString | @Composable () -> Unit)

. or implicit conversions (which is more powerful for better or worse

Question: How can you make a VerticalScroller stay scrolled to the end of the list as new data is added? Right now my data is added but the list does not move.

VerticalScroller(
            isScrollable = true,
            child = child
        )

I'm getting a weird Kotlin compiler error? Anyone know how to solve these?

Internal error: Couldn't inline method call 'state$default' into @androidx.compose.Composable public inline fun <T> `state$default`(noinline areEquivalent: ((T, T) -> kotlin.Boolean)?, init: () -> T, `$mask0`: <http://kotlin.Int|kotlin.Int>, `$handler`: kotlin.Any?): androidx.compose.MutableState<T> defined in androidx.compose <no source>

Heya! I’m having trouble wrapping my head around centering a view vertically in dev06. It looks like this and my code is like this…

Row {
        // ...
        Container(width = 48.dp, height = 48.dp) {
            DrawVector(profilePlaceholderImage)
        }
        Spacer(modifier = LayoutPadding(start = 16.dp))
        Column {
          //  ...
          drawNameAndStars()
        }
// This line of code isn't working as expected 
        Container(width = 14.dp, height = 14.dp, modifier = LayoutFlexible(1f) + LayoutAlign.CenterRight) {
            DrawVector(arrowVector)
        }
    }

Have method references stopped working? I'm trying to pass an @Composable function via method reference, and it fails to run (or compile, depending on how I define the withView function):

io.khimera.example.weather.SplashScreenViewModelKt$splashScreenRouter$1$1 cannot be cast to kotlin.jvm.functions.Function2

fun <T> withView(view: T) where T:(@Composable() (VM) -> Unit)  {
        if (this.view != null) throw IllegalStateException("Route already has view")
        this.view = view
    }

...
withView(::SplashScreen)

I would like to request the compose team for a fractional layout modifier. Its works better than LayoutOffset because I don't have to manager pixels. Its make sense?

data class LayoutFractional(val dx: Float, val dy: Float) : LayoutModifier {
    override fun ModifierScope.modifyPosition(
        childSize: IntPxSize,
        containerSize: IntPxSize
    ): IntPxPosition = IntPxPosition(
        x = childSize.width * dx.coerceIn(MIN_FRACTION, MAX_FRACTION) *
                if (layoutDirection == LayoutDirection.Ltr) MAX_FRACTION else MIN_FRACTION,
        y = childSize.height * dy.coerceIn(MIN_FRACTION, MAX_FRACTION)
    )

    companion object {
        private const val MAX_FRACTION = 1f
        private const val MIN_FRACTION = -1f

        val Origin = LayoutFractional(0f, 0f)
    }
}

Hi, is there any support for nested scrolling like NestedScrollView { RecyclerView } ? Right now I’m using a VerticalScroller wrapping an AdapterList which results in a screen with endless scrolling.

Can we use Lottie in Jetpack Compose?

Hey. Is there some place with a description of Frame and Model concepts? What is the supposed way to modify Model? As I understand compose callbacks like onClick are executed in scope of Frame, but how to manage such scopes outside of such callbacks (from IO events, for example). Thank you.

I made an expand-collapse button. sharing it here in case it might be useful for anyone. (It's easy & fun to make with Compose!) https://gist.github.com/pt2121/3fa9e0e3e2659171102d752b33d1b1c7

Is compose accepting pull request?

Any feedbacks are welcome https://github.com/programadorthi/compose-weather-forecast

This might have been answered before, but given the current need for a successful build in order to have a working preview, does it worry you guys that Compose may become unsustainable in larger apps that have a build time greater than one minute? Is anything in the works so that something like a "real-time pre-build" sort of thing allows for a reasonable fidelity preview or something else?

i was hoping that compose would have a hot reload (similar to react native or flutter) but looking at android studio preview it looks like that will not happen. anybody knows if compose will support hot reload in the future? (also, if there is a project w/ hot reload in android ecosystem please share)

The

drawLayer

modifier is real nice! https://gist.github.com/zach-klippenstein/e2c8e6edf0d950d8ba527cd0681c5b60