Jasmin Fajkic
09/07/2022, 7:55 AMHasan Nagizade
09/07/2022, 8:17 AMJohn O'Reilly
09/07/2022, 8:39 AMSimon Wanbua
09/07/2022, 9:30 AModay
09/07/2022, 10:21 AMYves Kalume
09/07/2022, 10:54 AMSlackbot
09/07/2022, 12:13 PMColton Idle
09/07/2022, 1:33 PMhttps://youtu.be/SWBN0y0lFNY▾
deviant
09/07/2022, 1:45 PMJason Atwood
09/07/2022, 2:41 PMThe only time a read can't happen is when reading ahttps://dev.to/zachklipp/implementing-snapshot-aware-data-structures-3pi8 A year later, do you still agree w/ the statement "although in practice it usually means a bug in Compose itself, not your code" ?that was initialized after the current snapshot was created. If you've ever gotten anStateObject
with the message "Reading a state that was created after the snapshot was taken or in a snapshot that has not yet been applied", that might be why (although in practice it usually means a bug in Compose itself, not your code)IllegalStateException
Aaron Waller
09/07/2022, 3:14 PMnitrog42
09/07/2022, 3:41 PM```* @param sheetPeekHeight The height of the bottom sheet when it is collapsed. If the peek height
* equals the sheet's full height, the sheet will only have a collapsed state.```What is the best way to set it to the “sheet full height” ? use Modifier.OnSizeChanged {} on the sheet content ?
Afzal Najam
09/07/2022, 8:04 PModay
09/07/2022, 9:14 PMAkram Bensalem
09/07/2022, 10:15 PMzt
09/07/2022, 11:08 PMColton Idle
09/07/2022, 11:23 PMStaggeredGrid
(Ia48be)
• Renamed <http://FocusDirection.In|FocusDirection.In>
and FocusDirection.Out
to FocusDirection.Enter
and FocusDirection.Exit
(Ia4262, b/183746982)
• Introduced a rememberSnapFlingBehavior
overload that provides a quick way of enabling snapping in LazyLists
. (Ifb48a) if this is what I think it is... OH HECK YEAHHH. EDIT: Actually I want snapping in non-lazy lists. Snapping in lazy lists can already be done with chris banes snapper. But maybe this opens the door for non lazy snapping?
• Swipeable V2 (Phase 1) (👀 jossi)
• Gradle edition: kotlin.RequiresOptIn is now enabled by default (not exactly sure what this means, but hopefully no more kotlin warnings about experimental apis?)
Material3
• Default components insets introduced in m3 components in beta01 version no longer account for IME insets.
• Material3 Scaffold component now has a contentWindowInsets
parameter, allowing to specify the amount of insets to handle for the content slot. (Icf11a, b/243713323)
• Deprecates the experimental Material 3 SmallTopAppBar
function and introduces an equivalent TopAppBar
function. Please migrate your usage to the new one. (I74404, b/226918634)
• Adds control over the top app bar fling and snap behaviors. (I15c81)
• Removes startIndent from Divider, moves color to last parameter. (If7be2)
• Have Dialogs identify themselves to talkback users by announcing the word Dialog when they are displayed.
Oh and compiler version update today too
• Fix IllegalStateException
where Compose Compiler was erroneously marking unit types as composable in some circumstances. (b/237863365)
• Users must now specify their preferred Kotlin version when suppressing compiler version check (I9e5e2)Slackbot
09/08/2022, 2:10 AMMjahangiry75
09/08/2022, 9:41 AMOthman El Jazouli
09/08/2022, 10:34 AMscrollable
modifier, is there a way to have the same for lazycolumn?Aaron Waller
09/08/2022, 11:29 AMZun
09/08/2022, 11:33 AMAaron Waller
09/08/2022, 12:19 PMTim Malseed
09/08/2022, 12:24 PMSavedStateHandle
of the previousBackStackEntry
and then popping the backstack.
But, the SavedStateHandle
that I want to interact with belongs to the initial screen’s ViewModel
, and I sense that this is not the same instance as the SavedStateHandle
found on the previousBackStackEntry
I suspect this has something to do with scoping ViewModels
, but I’ve tried a few things and I’m out of ideas. Code in threadColton Idle
09/08/2022, 1:45 PModay
09/08/2022, 2:52 PMactive
flag is false, and 1 if it’s true, is there a nicer way to do it than adding alpha = if (active) 1f else 0.5f
to each composable inside?Jasmin Fajkic
09/08/2022, 3:06 PMallan.conda
09/08/2022, 3:19 PMjim
09/08/2022, 11:01 PMZoltan Demant
09/09/2022, 4:21 AMAnimatedContent
is not animating my content in a given scenario, despite targetState
having changed. It works in all other cases. Any ideas? More details in 🧵Zoltan Demant
09/09/2022, 4:21 AMAnimatedContent
is not animating my content in a given scenario, despite targetState
having changed. It works in all other cases. Any ideas? More details in 🧵slideInVertically + fadeOut
and slideOutVertically + fadeIn
.Ian Lake
09/09/2022, 4:29 AMcollectAsState()
then an if (data != null) { DetailScreen(data) }
, then you'll just be animating out an empty screen, which doesn't seem like what you'd wantZoltan Demant
09/09/2022, 4:31 AMdataFlow.take(1)
on the parent, then the animations runs fine 🤷♂️🏽 So definitely seems to be related to that, but I cant tell how. Ive gone through the entire loop multiple times and everything works exactly as expected.. basically: delete happens, cache is updated, triggers related flows to refresh, screen is updated.Ian Lake
09/09/2022, 5:00 AMresult.onSuccess { updateState }.onFailure { navigateBack }
call, did you log how many times the onSuccess
and onFailure
lambdas are being called? It would be interesting to know if you're somehow calling navigateBack
multiple times in a rowZoltan Demant
09/09/2022, 5:23 AMwithContext(IO)
block, and the result of that was then handled inside another withContext(IO)
block (my intention was to have both of those in the same block).
Theres literary no code outside the withContext blocks, and the entire call is invoked on Dispatchers.Default
. Id love to understand how that could have such an impact on this scenario! I also understand if thats impossible to say without way more details, all in all Im just glad that it works as expected 🙂