kotlinlang #compose

is required when updating the state (from Android View callbacks for example) in order to propagate updates, but I don’t understand why it’s required in this case… 🤔

zsperske

11/29/2021, 9:38 PM

How do I make the decision on where to navigate outside of my composable? Say I have some card:

Card(onClick = { viewModel.postEvent(EventListUIEvent.EventSelected(eventState.event)) } )

I want to make a decision on where to go next without my composable knowing about its potential destinations.

jeff

11/29/2021, 10:41 PM

Modifier.alpha(0f)

the Compose equivalent of

View.INVISIBLE

? In regards both to performance and things like screen readers? Is there something better I should be doing?

Arsen

11/29/2021, 11:16 PM

What would happen, if Snapshot#*nextSnapshotId* reach max value? Next increment resets it to zero due to overflow, so "monotonically increasing" rule will break?

brabo-hi

11/30/2021, 12:16 AM

Hi all, when using compose material3, how could we launch snackbar since the ScaffoldState doesnt have

scaffoldState.snackbarHostState

it only has

drawerState

👀 1

amiracam

11/30/2021, 3:57 AM

I'm interested in Jetpack Compose multi platform but the objective is from one code base to deploy both a desktop and web app, is that currently possible ? much thanks

K Merle

11/30/2021, 7:38 AM

Anyone know how to do a chat bubble shape with an arrow on a side in Compose?

Johan Reitan

11/30/2021, 10:24 AM

I’d like to handle a navigation result in a

ViewModel

. I expected that I could use the

SavedStateHandle

injected in my

ViewModel

to listen to the navigation result, but I see that this

SavedStateHandle

is not the same as the one from the

NavBackStackEntry

that holds the result. Details in thread 🧵

Erlan Amanatov

11/30/2021, 11:10 AM

Hi everyone. Just finished working on this little project with some cool animations, it was a joy to work with jetpack compose. I'm pretty pleased with the result. Original idea and design . Link to my repository . :kotlin-intensifies::jetpack-compose:

rateIt60.mp4

😂 10

🙌 3

👍🏻 1

😁 8

:kotlin-intensifies: 6

😱 6

👍 17

👍🏼 1

🙌🏻 1

🙌🏾 1

Samir Basnet

11/30/2021, 12:21 PM

val scrollState = rememberLazyListState()
val lazyInsuranceItems = pager.collectAsLazyPagingItems()
LazyColumn(state = scrollState) {
    itemsIndexed(lazyInsuranceItems) { index,insurance ->
        InsuranceCell(insurance!!) {
            navController.navigate("InsuranceDetail/${insurance.id}")
        }
    } }

Trying to create list and detail screens as above but on returing to list the scroll position is lost and returns to top. Can anyone guide me on how to maintain scroll position?

Tim Malseed

11/30/2021, 12:27 PM

Hi all, I’ve got a bug in testing Compose navigation that I’ve been trying to solve over the course of the past week. I suspect there’s a bug in the testing framework. If someone could help confirm that, I’d be happy to file a bug report. I’m getting a crash when one of my tests runs after another test. It seems that there’s some lingering state or something going on. Both tests can be run in isolation and pass. But one test fails if run after the other. Code in thread

Paul

11/30/2021, 1:08 PM

Hey everyone. I'm trying to achieve a simple animation with text expanding and collapsing. However, I've stumbled across the problem I'm not sure how to solve. Thread 👇

Arsen

11/30/2021, 1:23 PM

According to comment, it doesn't clear, that calling "dispose" is mandatory at the end of Snapshot's lifecycle, it seems more like optional which is not.

iamthevoid

11/30/2021, 1:32 PM

I have a problems with snap behavior in accompanist view pager. Sometimes when i swipe pager with finger it doesn’t scroll until page bound and remains at same position where i leave it whn scroll with finger. Is there something special about finger scrolling? when i use

state.animateScrollToPage

all works correct

Brian G

11/30/2021, 1:39 PM

How can we call WebView.destroy() within Compose? When using AndroidView+WebView. Does it even matter?

Archie

11/30/2021, 2:03 PM

Hi Guys, Whats the best approach for NavGraph where a combination of Persistent TopAppBar and/or BottomNavigationBar but you also need a Full Screen that provide its own TopAppBar/BottomNaivgationBar?

Kiprop Victor

11/30/2021, 2:06 PM

Hi, I have a list of items that I want to iterate through one at a time via clicks and display its content in a composable:

🧵 2

Colton Idle

11/30/2021, 3:04 PM

Is there any chance to write this

style = MaterialTheme.typography.h1,

but have the "h1" be a variable. like val myStyle = "h1" then have

style = MaterialTheme.typography.+myStyle

Slackbot

11/30/2021, 5:46 PM

This message was deleted.

brabo-hi

11/30/2021, 6:20 PM

When using Scaffold on compose material 3, how could we dock floating action button ?

theapache64

11/30/2021, 7:04 PM

Navigation Compose + Hilt: 💉 How can I do

@AssistedInject

with Navigation Compose’s

hiltViewModel

method? More Info ➡️ 😒tackoverflow: https://stackoverflow.com/questions/70174711/how-to-do-assisted-injection-with-navigation-compose

jeff

11/30/2021, 8:41 PM

Can anyone recommend some reading about what parts of a composable will recompose when, and why, and how to avoid recomposition, that sort of thing?

Joseph Hawkes-Cates

11/30/2021, 10:50 PM

Good evening, compose friends. I’m running into a discrepancy with a Box where it lays out differently on device than in preview or interactive mode. See thread for more info…

Chris Fillmore

11/30/2021, 11:09 PM

Is it possible to position an element on a bottom sheet so that it always sits on the bottom of the screen, regardless of whether the sheet is in

HalfExpanded

Expanded

state? In particular, what I observe is that when the bottom sheet content is more than 50% of the screen height, and the bottom sheet is

HalfExpanded

, then the element is positioned below the bottom of the screen (not visible). If I drag it to

Expanded

state, then the positioned element becomes visible. For example:

// I'm using bottom sheet navigation
bottomSheet(...) {
  Box {
    Column {
      // Some content here
    }
    Row(
      // Alignment from BoxScope
      modifier = Modifier.align(Alignment.BottomCenter)
    ) {
      // I have some buttons I want to put here that will remain at the bottom of the screen while the bottom sheet is open
    }
  }
}

ursus

12/01/2021, 12:38 AM

How to make this UI performant? Naively ofcourse its trivial, its a Column of N Cards, where each Card is a Column of M Items Making it LazyColumn of N Cards helps, however, each Card can be unboundedly big (i.e. number of Items is not fixed) Is there a way to make the each item within Card recycleable? Or try to fake it via flattening it into List<ListItem> and adding horizontal ui to each item to make it appear its nested in a parent, when its not?

Colton Idle

12/01/2021, 4:22 AM

I'm looking at ways to specify a modifier conditionally. I found two samples in this slack. 1.

inline fun Modifier.modifyIf(condition: Boolean, then: Modifier.() -> Modifier): Modifier =
    if (condition) then() else this

inline fun Modifier.thenIf(condition: Boolean, block: () -> Modifier) =
    this.then(if (condition) block() else Modifier)

Number 1 does not work for me (it actually messed up my modifier), while number 2 works exactly as expected. I'm not sure why. Any ideas?

Filip Wiesner

12/01/2021, 8:18 AM

Is there a way to use only enter (or only exit) animation in

AnimatedVisibility

? I tried

fade

with

tween(duration = 0)

but there is still small delay before the view disappears.

Slackbot

12/01/2021, 9:11 AM

This message was deleted.

Marcello Galhardo

12/01/2021, 1:55 PM

If I have a single (complex) state in a VM and I observe it from my Composable: all the views that observes any property of this state will always be recomposed on any emission or compose somehow is capable to discover that only a single piece of that state changed (with some sort of diff)? I'm not sure how to debug a recomposition, tips are welcomed! 🤔

Michal Klimczak

12/01/2021, 2:14 PM

I have a feeling that the change that made accompanist Pager based on LazyRow / LazyColumn introduced a lot of issues. And it's a bit difficult to understand what is the team's current stand on this, the issues on github didn't receive any attention lately. Downgrading is painful, as the compatibility with compose (and therefore the kotlin version) usually needs to be pretty strict. I started wondering if I should maybe get the

0.18.x

version and try to make it compatible with new compose. Anyone knows what is the roadmap here?

Title

Michal Klimczak

12/01/2021, 2:14 PM

0.18.x

version and try to make it compatible with new compose. Anyone knows what is the roadmap here?

12/01/2021, 2:19 PM

What issues are you referring to? Some of them are probably working as intended

Michal Klimczak

12/01/2021, 2:21 PM

this one is mine: https://github.com/google/accompanist/issues/876 but I skimmed over issues list and there's lots of recent pager-related ones

"older" pager had the same issue, which you fixed, but switching to LazyRow reintroduced it

Stylianos Gakis

12/01/2021, 2:26 PM

This one as well, we actually downgraded to 0.18.0 because of it.

Andrey Kulikov

12/01/2021, 2:45 PM

I am going to triage those bugs soon. lets discuss each issue individually in the corresponding bugs. but if you think the new implementation absolutely doesn’t work for you you can just copy the implementation from 0.18 into your project. for example I am not yet sure how to implement the page skipping described here https://github.com/google/accompanist/issues/876

👍🏽 1

:thank-you: 1

Michal Klimczak

12/01/2021, 2:47 PM

yeah, I thought it might be tricky for LazyRow... I can actually wait a week or two, if nothing interesting comes up, will copy, thanks for letting me know :)

View count: 2