Uli Bubenheimer

Actually, for the purpose of troubleshooting you could pass the MutableState into the Map() Composable; there is a small issue in Compose with using `rememberUpdatedState()` crossing nested composition boundaries; there...

I'd just pass the MutableState into the Map() composable instead to work around a Compose bug with rememberUpdatedState() in this case. It's just that you recompose almost everything every time...

I guess what I suggested about `selectedLocationIndex` may not be enough, as it's accessed everywhere anyway. You could create a boolean MutableState somewhere outside all those composables, outermost loop element,...

It's a derivedStateOf for index == selectedLocationIndex, but that only works if selectedLocationIndex accesses a State

I should stop commenting and leave it to the project maintainers. Your `LaunchedEffect(pagerState.currentPage)` was fine, actually, I just would instead do `LaunchedEffect(pagerState) {...}` with a snapshotFlow in the lambda. It's...

I recommend not using `rememberMarkerState()`, and replacing it with `remember { MarkerState(...) }`, as the former uses rememberSaveable, which is not what you want when you render markers from a...

Also, I don't think the key in rememberSaveable/rememberMarkerState works like a key() block, so the latter will help indeed.

Personally I'd be in favor of eliminating `rememberMarkerState` entirely. I find it misleading and an anti-pattern: https://dev.to/bubenheimer/effective-map-composables-non-draggable-markers-2b2#:~:text=Be%20aware%20that,recommend%20ignoring%20it. https://dev.to/bubenheimer/effective-map-composables-draggable-markers-3bea#:~:text=This%20behavior%20is,with%20a%20model.

Behavior unchanged in 2.5.0 release

This issue also exists in media3 1.1.0-alpha01. NB I use a custom player based on SimpleBasePlayer. Also, I see that MediaSession.Callback onConnect() and onPostConnect() are called twice for some reason,...