I have an issue with a

Slider

in scrollable list. When I start to scroll the list and hit slider’s track in the way, the thumb jumps to that position immediately and scroll also happens. Is there a way to workaround this problem? For example, for buttons such problem doesn’t exist. When I hit button when starting to drag, it doesn’t actually trigger

onClick

(the ripple effect is rendered anyway though).

Hi 👋 Is there any way to draw compose to bitmap? I tried to put Compose in View and use Bitmap canvas to draw View. I got a mess with backgrounds in bitmap but the same View was drawn properly on display 😬

I am trying to make a single item clickable list. But the radio button never show selected until I scroll the items. Any help? https://stackoverflow.com/questions/67961422/lazycolumn-item-with-radiobutton

Hi guys. My app architecture looks like: viewModel + Compose layout per screen. In my viewModels I have Channel() where I handle actions from screen:

init {
  viewModelScope.launch {
            try {
                actions.receiveAsFlow().collect { action ->
                    when (action) {
                                    //handle actions here
                   }
              }
        }
}

In

Home screen

I have list with post. The problem is when I select post and navigate user to

PostDetails screen

I can choose another post though list with post is underhood. I think it's related to

Home viewModel

and that action flow works in the background. Any solution what should I change?

Is binding the current value of a piece of state to a local variable so that the compiler can infer it isn't null a valid pattern, or is there a better way to do this?

val trackSettingsState = repo.trackSettings().collectAsState(initialValue = null)
val trackSettings = trackSettingsState.value

if (trackSettings == null) {
   Spinner()
}

TextField(trackSettings.frequency, /* ... */)
Text(trackSettings.name)

I could also use a with statement or an else branch, but I prefer handling the null-case up front and then being able to assume it isn't null later

Hi there, how do you detect soft keyboard visibility changes? On stack overflow some solutions are using the global layout listener, but I really don't like this solution because this method is called many times. The only "good" solution I have found is to use WindowInsets in the onCreate method of my main activity:

ViewCompat.setOnApplyWindowInsetsListener(window.decorView) { _, insets ->
    val isKeyboardVisible = insets.isVisible(WindowInsetsCompat.Type.ime())
    onSoftKeyboardVisibilityChange(isKeyboardVisible)// own method which notifies me of changes
    insets
}

This way worked in the emulator (Pixel 3a API 30) but not on my phone (Galaxy S8 API 28) On top of that after launching my app, I noticed that my statusBarColor and navigationBarColor from themes.xml no longer work (status and nav bars are white or dark according to the theme instead of my own colors set in themes.xml) I tried to change

window.navigationBarColor

and

window.statusBarColor

in the setContent without success I don't understand what's going on. Is it possible to have an explanation ?

Is there a way to automatically rotate Icons when the device is using a RTL language? I can turn on

AutoMirror

for my own vector drawables but cant find a way to do that for Material Icons

Hey all, I’m currently working with accompanist and the insets libraries, and it’s mostly doing what I want. Though I ran into a particular use case where passing padding from the insets-ui

Scaffold

to a child

Composable

isn’t very obvious More info in the thread…

Hi, I started reading the ‘Foundation’ articles and I’m having some difficulties in understanding how things build up from source code to runtime execution. Specifically, consider the following quotes: “In Compose's declarative approach, widgets are relatively stateless and do not expose setter or getter functions. In fact, ***widgets are not exposed as objects.***” “Composition: a description of the UI built by Jetpack Compose when it executes composables.” “remember (composable) stores objects in the Composition, and forgets the object when the ***composable*** that called remember is removed from the Composition.” What exactly does the Compose compiler produce when parsing a @Composable annotated function ? Does it generate a class for each function that gets instantiated at runtime as node in the UI object tree ?

Does this mean that the next version of Compose cannot be used with AGP 4.2?

Is there an empty element in compose?

Hi. Is there any possibility to disable dragging in

ModalBottomSheetLayout

? I'm looking for solution that would allow to hide bottom sheet only programmatically.

I need to fill the remaining space in

Column

with an image but with a limit of its height. My code looks like

Column{
item1()
item2()
Image(Modifier.weight(1f))
item3()
..
)

For small screens it works fine, but on bigger screens it takes too much space. So I need to limit the height of the image somehow.

Does anybody know if there’s a way to force a compositing layer for a composable without a hack like setting alpha to 99%?

There is any way i can scroll to a specific item inside a LazyColumn ?

I am trying to pass Parcelable from master to detail view. I found out that

arguments

is null when I use

putParcelable

so I first have to instantiate it with

Bundle()

. Am I doing something wrong? I do not see any example with this mention ...

Has anyone run into an issue where their TextField won't get focus from a DisposableEffect in beta-08? I'm trying to focus the TextField on fragment start but when I check the focus it says it's not focused. I'm using a FocusRequester and made sure nothing should be interfering in it receiving focus. It pops the keyboard up but the cursor isn't there which means its not active. It works fine if requested from a button click or some event firing... but on initial composition it seems there's a bug with this

DisposableEffect(Unit) {
    focusRequester.requestFocus()
    onDispose { }
}

This is kind of a compose question and kind of an android question. The compose app I’m working on recently underwent security testing and one of the issues brought up was

Activity androidx.compose.ui.tooling.preview.PreviewActivity is not protected [android:exported=true]

. I was trying to find out why it’s important for the

PreviewActivity

to be exported or if I can make it not exported for my project. As far as I can tell setting

android:exported=false

for the

PreviewActivity

only affects deploying a

@Preview

to the device. Will making this change have any negative effects on a release build of the app? If this is a non-issue, is there a link to release notes/documentation as to why it isn’t an issue?

in a full complete compose app, where strings will be saved, in Strings.kt as const or what, if this is the case what about the Localization part, pardon my ignorance if it was a basic question but I just got started

Hey folks 👋 - we’re currently porting our design system from views to compose and I’m kinda missing the equivalent of

firstBaselineToTopHeight

in the compose world. I would’ve expected it near

lineHeight

in a

TextStyle

. Is it currently missing and is there any chance this will be supported any time soon? 🙂

I'm currently use "TabRow" and "HorizontalPager" I wonder how to scroll the Tab idicator when switching from screen to another screen 🤔🤔

Hey I have a quick question how something bothering me for some time assuming :

val pagerState = rememberPagerState(pageCount = 2)

can we write

val selectedTabIndex = pagerState.currentPage
TabRow(selectedTabIndex = selectedTabIndex,...)

or do we have to do :

val selectedTabIndex = remember(pagerState) { pagerState.currentPage }

?

If I have a transitive

remember

's which are initialized with values of

State<T>

, will they be re-memoized on state changes? This sounds quite entangled, that's because I need some clarity on this 🙂 Please see thread, with bottom-sheet related example.

I’m impressed that I found no reference for

RelocationRequester

here in the channel 😄 I have a

Column

with several

TextField

. When I tap on a

TextField

at the bottom of the screen, the keyboard is opened and I want that field be positioned just above the keyboard. I thought that

RelocationRequester

resolves this problem…

I have a

class ProjectsViewModel : ViewModel()

and i already called it in a component using :

val projectsViewModel: ProjectsViewModel = viewModel()

and when i navigate (using Navigation Component) and try to get the model using the same viewModel through different components ? Or should i declare the instance in the top of my code and pass it to different component that need access to it ?

I've multiple network requests in single screen having different observers as below

val user by remember(profileViewModel) { profileViewModel.user }.collectAsState()
val posts by remember(profileViewModel) { profileViewModel.posts }.collectAsState()

when (user) {
	is UiState.Loading -> {
		CircularProgressIndicator(
			modifier = Modifier.wrapContentWidth(CenterHorizontally)
		)
	}
	is UiState.Success -> {
		(user as UiState.Success).data?.let {
			ProfileView(user = it)
		}
	}
}

when (posts) {
	is UiState.Loading -> {
		CircularProgressIndicator(
			modifier = Modifier.wrapContentWidth(CenterHorizontally)
		)
	}
	is UiState.Success -> {
		(posts as UiState.Success).data?.let {
			PostView(post = it)
		}
	}
}

How do i make sure that

PostView()

is drawn below

ProfileView()

?

Is there an easy way to make my transparent topBar overlay the content in my Scaffold, or do I manually need to add my toolbar+content in a box?

SaveableStateHolder does not restore 

rememberSaveable

 values after process death when it is wrapped with a 

CrossFade

 animation - https://issuetracker.google.com/issues/191059138 Can anyone verify this?

What is the preferred approach • pass

ViewModel

as a param to the composable • use

Koin

to inject

ViewModel

Can you point out pros & cons also because I don't see much of a difference