Are there plans from JetBrains for a multiplatform crypto library? Iirc it was one of the most upvoted features here in slack, when someone from JetBrains asked for missing features.

Hello! I am trying to load a layer-list drawable with this code:

Image(
    painter = painterResource(id = someId),
    contentDescription = null
)

but i get this error:

Only VectorDrawables and rasterized asset types are supported ex. PNG, JPG

. I can load vector drawables so I suppose that I need to load layer-list differently... How is this possible?

How to call rest API using kotlin multiplatform desktop app? Any one have Github demo?

How can I disable

HorizontalPager

scroll (via

userScrollEnabled

) when the user started a

LazyColumn

scroll (and vice versa)? Do I need to write a complex

NestedScrollConnection

?

Will Apple let KMM succeed? Effectively, Multiplatform Compose and KMM will make iOS Developers, XCode or Swift obsolete. So, what is in it for them? And what guarantees the Kotlin Multiplatform approach will be possible to be used for development in 2-3 years?

Is it possible to make a sealed class parcelable? I’ve annotated the child classes with `@Parcelize`but when I add the annotation to the parent, I get an error saying “Parcelable should not be a ‘sealed’ or ‘abstract’ class”

Hi People! How do you load image resources in your compose ios app ?

is there any way to disable paste on a TextField?

>

Experimental context receivers are deprecated and will be superseded by context parameters. Please don't use context receivers. You can either pass parameters explicitly or use members with extensions.  
> 
> See new context parameters proposal: <https://github.com/Kotlin/KEEP/blob/context-parameters/proposals/context-parameters.md>. During the transition period, neither context receivers nor context parameters will be supported. This warning will become an error in future releases.

As a quick straw poll, how are most of us

context-receivers

lovers expecting to handle the migration? 1️⃣ go full ostrich, ignore it, stick to the last kotlin version that supports

context-receivers

and hope we can wait out the kotlin release that enables

context-parameters

2️⃣ stop using

context-receivers

for the time being, revert to

.bind()

et al, or where possible use

Raise<E>

as an extension receiver 😭 find a corner and cry until it all blows over

Is there any plan to support edge-to-edge on iOS and Android platforms under Compose Multiplatform? Or if there is any existing implementation/library, I'd like to know about it.