Marquee is supported now????? 😮 I've been trying to come up with a way to do it properly and it's finally a real thing!

In case you haven't seen it. We released Compose 1.4 stable and Compose BOM March Release today. 😛arty-parrot: https://android-developers.googleblog.com/2023/03/whats-new-in-jetpack-compose-march-23-release.html

Why is

resources()

marked as internal in androidx.compose.ui.res ? I am in a place where I need to decide on a string to be used inside my ViewModel. As described here, I am only exposing the StringRes Int from there, and I need to then resolve that string inside my composable. Specifically, I am outside of a composable context since I am resolving it inside a lambda, so I can’t just use the

stringResource()

function which uses this function internally. So it turns out I need to do what

stringResource()

does interally myself, which is

LocalConfiguration.current
return LocalContext.current.resources

So that I make sure I read LocalConfig in order to make sure I do not grab stale data.

resources()

already exists and does this exact thing, but it’s marked as internal, shouldn’t that just be a public function?

Isn't touch still supported in UIKit interop in Compose Multiplatform? I add a Mapview to the view, but I find that I can't operate it with gestures. Have any of you encountered similar problems?

When in ColumnScope for example, if I need to have a AnimatedVisibility, for the contents of it, they don’t “inherit” this column scope, and they are laid out on top of each other. To mitigate that you need to have another column in there to make it work as you want it to. Something like this:

Column {
  Stuff()
  AnimatedVisibility(shouldShow) {
    Column {
      Text()
      Spacer(Modifier.width(8.dp))
      Icon()
    }
  }
}

But when doing this with CompositionLocalProvider like this:

Column {
  Stuff()
  CompositionLocalProvider(LocalContentColor provides LocalContentColor.current.copy(alpha = ContentAlpha.medium)) {
    Text()
    Spacer(Modifier.width(8.dp))
    Icon()
  }
}

You don’t need to do this, it just works. Why is this the case?

CompositionLocalProvider

isn’t even inline or something like that, nor is it an extension on ColumnScope for it to work due to that. So how does it work? What am I missing here?

does any1 know how to use the new Api LazyLayoutPinnableItem ?

Not that I know of

https://github.com/thellmund/Android-Week-View/issues/299#issue-1637184622 Has anyone used this library and facing the same issue?

Does anyone know how to properly handle bottom sheets in a hybrid app (part xml, part compose)? Basically the issue is that ModalBottomSheetLayout cannot scrim content that is not part of it’s child content, nor can it or BottomSheetScaffold have the sheet cover content that is not part it’s child content. In a hybrid type of app, the compose portion is likely not to be in control of the entire screen. Would the recommendation still be to use BottomSheetDialogFragment and BottomSheetBehavior, but have the views be written in compose?

It seems there is yet another focus regression in compose-ui:1.4 😰

E  java.lang.IllegalStateException: Check failed.
    [Full trace in thread]
   	at androidx.compose.ui.focus.FocusOwnerImpl.moveFocus-3ESFkO8(FocusOwnerImpl.kt:150)
   	at androidx.compose.ui.platform.AndroidComposeView$keyInputModifier$1.invoke-ZmokQxo(AndroidComposeView.android.kt:212)

Compose 1.4.0 stable released yesterday 🎉 Also, 1.1.0-beta01 of m3 • Updated the

DateRangePicker

to allow selecting a range with the same date for its start and end. (I16529, b/272882497) • Text fields now properly position their text elements when font size is smaller than expected. This may result in a few pixels change in your apps based on font settings and script. (I8b8d0) • Add layout type param to

TimePicker

composable. It allows to use different layouts, depending on the screen configuration (Ia0e16) • Added shadow elevation to

BottomSheetScaffold

(I94e0f) • Added support for displaying the date pickers without the header part And first releases of 1.5.0 (alpha 01) •

AnimatedContent

APIs are now stable

AnimatedContentScope

has been renamed to

AnimatedContentTransitionScope

.

scaleIn

and

scaleOut

are now stable APIs. (Iaf54e) • Text and

BasicText

is refactored to use the new modifier system. This leads to substantial performance improvements in many cases. No changes should be visible. (If1d17, b/246961435) • Added the

PerformImeAction

semantics action to invoke the IME action on text editor nodes. (IDK what this does, but sounds sorta importatnt?) • Add a chipgroup reflow sample. Update the horizontal padding in between child chips in the single line chipgroup sample to match spec. (I3b155) • Fixed an issue where

ModalBottomSheetLayout

would crash in an edge case on orientation change. Layout animations (e.g.

Modifier.animateContentSize

) in/on the sheet content now work smoothly. (I2f981, b/266780234) • Adds

Modifier.Node#coroutineScope

to allow

Modifier.Nodes

to launch coroutines (I76ef9) • Allow

Modifier.Nodes

to read

CompositionLocals

by implementing the

CompositionLocalConsumerModifierNode

interface. (Ib44df) • LookaheadLayout has been replaced by LookaheadScope, which is no longer a Layout. This allows chid content in a LookaheadScope to be directly controlled by parent's MeasurePolicy. (Ibe2e5)

Looks like Material3

BottomSheetScaffold

has had a regression - it used to work fine with a LazyColumn but now the dragging of the sheet is broken if you do it in the bounds of the LazyColumn. Min repro in 🧵

Just learned that in compose UI 1.3.3, at least, trying to draw a text on a DrawScope off the canvas causes a crash. The latest androidx main appears to have the same code, so likely will crash as well.

Does someone know if the Layout Inspector supports Jetbrains compose libraries for Android? They do not seems to work for me.

can jetpack compose motion scene xml have different start and end destination? can you share a info or link to any doc?

Hello guys, can i use early returns inside @Composable to conditionally add UI elements?

Hello, can someone help me understand why I'm getting

java.lang.IllegalStateException: Reading a state that was created after the snapshot was taken or in a snapshot that has not yet been applied

for this composable when doing a state read in the layout scope. The problem doesn't occur when I change using

graphicsLayer

from the lambda style (layout layer update) to the parameters arguments one (composition layer)

Is it OK to use

@ReadOnlyComposable

if the function only reads a

State

value?

How can I limit the size of input of TextField? in XML I used

InputFilter

something like this:

val limitSizeInputFilter = arrayOf<InputFilter>(ByteLengthFilter(100, "UTF-8"))

binding.nsetName.filters = limitSizeInputFilter

Is there any equivalent to it in compose?

Is there a way to get a Drawable from a ImageVector? I want to use something like

androidx.compose.material.icons.Icons.Default.ArrowForward

as a placeholder for my Coil AsyncImage, but it only takes in a

@DrawableRes

or a

Drawable

. Looking for if I am missing some way to do ImageVector -> Drawable before I opt to use the SubComposeAsyncImage instead.

Hi everyone I have a question. How do I use a custom font in Compose multiplatform?

Hi everyone, I have a navigation drawer with a transaction report so whenever I press the "report" button in the nav drawer I want to fetch trasnaction using retrofit. I have a mutableList in my viewmodel and I update it with the data I get from the server. The problem is that in my screen I call getTransactions() and everytime the screen is composed this function is called over and over again. I understand the basic of compose and I know to handle states with remember, mutableStateOf etc., but I think I am missing something with lists. The exmaple I found are only shwoing how to fetch a one time list for example, a list of trivia questions and how to use it in the screen but not a test case where everytime you enter the screen you have to refresh the list and see if there are any new tranactions. Any ideas?

Looking at the material icons here https://fonts.google.com/icons?icon.query=device+unknown I can see that for example this “Device Unknown” icon exists. But in here, one can play with the settings, weight, fill and so on. Most importantly I am interested in the “Fill” one, which makes the icon look quite different when filled vs not filled. From the icons provided by the dependency

androidx.compose.material:material-icons-extended

I don’t see any such configuration being possible. None of the options

Filled, Outlined, Rounded, Sharp and TwoTone

seem to be doing this. Is there something I am missing or is this simply not possible at the moment?

Hey Composers! What's the state of dev on parallel composition execution? Is there an issue to track the progress on this?

Is it just me, or is "side effect" in Compose weirdly named? Usually, outside of compose world, side effect is kind of undesired behavior you would want to avoid.

I have a rather naive question purely out of curiosity :) Why does Compose make the reactive system so “complex”? Instead, couldn’t the Compose compiler analyze all composable functions that call

state

at compile time and records them, followed by inserting logic to update these composables after the corresponding “state operation”? Wouldn’t this approach effectively reduce the runtime overhead associated with recomposition?

For Material3 typography, when trying to dig into what is the default font style used, I see this line which simply says that the default is

TextStyle()

which internally does not specify the font size and so on, they are set as

TextUnit.Unspecified

. How do I know which typography value from the material3 typography is used by default if I simply call

material3.Text("blahblah")

without specifying the text myself? I know if I am in a contained which internally has set

ProvideTextStyle

it will be that, but what if I am not inside such a contained which has set that composition local? Couldn’t find anything in the m3 docs either for this.

Hi all, in navigation 2.6.0-alpha navController.backQueue is private so and I want to know navigation history how can I do?

Using the latest navigation 2.6.0-alpha07 im getting a strange exception when navigating without saveState, the strange part is it is triggered when having the navcontroller in the composable screen

java.util.NoSuchElementException: ArrayDeque is empty.
    at kotlin.collections.ArrayDeque.removeLast(ArrayDeque.kt:163)
    at androidx.navigation.NavController.launchSingleTopInternal(NavController.kt:1850)