https://kotlinlang.org logo
Channels
100daysofcode
100daysofkotlin
100daysofkotlin-2021
advent-of-code
aem
ai
alexa
algeria
algolialibraries
amsterdam
android
android-architecture
android-databinding
android-studio
androidgithubprojects
androidthings
androidx
androidx-xprocessing
anime
anko
announcements
apollo-kotlin
appintro
arabic
argentina
arkenv
arksemdevteam
armenia
arrow
arrow-contributors
arrow-meta
ass
atlanta
atm17
atrium
austin
australia
austria
awesome-kotlin
ballast
bangladesh
barcelona
bayarea
bazel
beepiz-libraries
belgium
benchmarks
berlin
big-data
books
boston
brazil
brikk
budapest
build
build-tools
bulgaria
bydgoszcz
cambodia
canada
carrat
carrat-dev
carrat-feed
chicago
chile
china
chucker
cincinnati-user-group
cli
clikt
cloudfoundry
cn
cobalt
code-coverage
codeforces
codemash-precompiler
codereview
codingame
codingconventions
coimbatore
collaborations
colombia
colorado
communities
competitive-programming
competitivecoding
compiler
compose
compose-android
compose-desktop
compose-hiring
compose-ios
compose-mp
compose-ui-showcase
compose-wear
compose-web
confetti
connect-audit-events
corda
cork
coroutines
couchbase
coursera
croatia
cryptography
cscenter-course-2016
cucumber-bdd
cyprus
czech
dagger
data2viz
databinding
datascience
dckotlin
debugging
decompose
decouple
denmark
deprecated
detekt
detekt-hint
dev-core
dfw
docs-revamped
dokka
domain-driven-design
doodle
dsl
dublin
dutch
eap
eclipse
ecuador
edinburgh
education
effective-kotlin
effectivekotlin
emacs
embedded-kotlin
estatik
event21-community-content
events
exposed
failgood
fb-internal-demo
feed
firebase
flow
fluid-libraries
forkhandles
forum
fosdem
fp-in-kotlin
framework-elide
freenode
french
fritz2
fuchsia
functional
funktionale
gamedev
ge-kotlin
general-advice
georgia
geospatial
german-lang
getting-started
github-workflows-kt
glance
godot-kotlin
google-io
gradle
graphic
graphkool
graphql
graphql-kotlin
graviton-browser
greece
grpc
gsoc
gui
hackathons
hacktoberfest
hamburg
hamkrest
helios
helsinki
hexagon
hibernate
hikari-cp
hire-me
hiring
hiring-french
hongkong
hoplite
http4k
hungary
hyderabad
image-processing
india
indonesia
inkremental
intellij
intellij-plugins
intellij-tricks
internships
introduce-yourself
io
ios
iran
israel
istanbulcoders
italian
jackson-kotlin
jadx
japanese
jasync-sql
java-to-kotlin-refactoring
javadevelopers
javafx
javalin
javascript
jdbi
jhipster-kotlin
jobsworldwide
jpa
jshdq
juul-libraries
jvm-ir-backend-feedback
jxadapter
k2-early-adopters
kaal
kafka
kakao
kalasim
kapt
karachi
karg
karlsruhe
kash_shell
kaskade
kbuild
kdbc
kgen-doc-tools
kgraphql
kinta
klaxon
klock
kloudformation
kmdc
kmm-español
kmongo
knbt
knote
koalaql
koans
kobalt
kobweb
kodein
kodex
kohesive
koin
koin-dev
komapper
kondor-json
kong
kontent
kontributors
korau
korean
korge
korim
korio
korlibs
korte
kotest
kotest-contributors
kotless
kotlick
kotlin-asia
kotlin-beam
kotlin-by-example
kotlin-csv
kotlin-data-storage
kotlin-foundation
kotlin-fuel
kotlin-in-action
kotlin-inject
kotlin-latam
kotlin-logging
kotlin-multiplatform-contest
kotlin-mumbai
kotlin-native
kotlin-pakistan
kotlin-plugin
kotlin-pune
kotlin-roadmap
kotlin-samples
kotlin-sap
kotlin-serbia
kotlin-spark
kotlin-szeged
kotlin-website
kotlinacademy
kotlinbot
kotlinconf
kotlindl
kotlinforbeginners
kotlingforbeginners
kotlinlondon
kotlinmad
kotlinprogrammers
kotlinsu
kotlintest
kotlintest-devs
kotlintlv
kotlinultimatechallenge
kotlinx-datetime
kotlinx-files
kotlinx-html
kotrix
kotson
kovenant
kprompt
kraph
krawler
kroto-plus
ksp
ktcc
ktfmt
ktlint
ktor
ktp
kubed
kug-leads
kug-torino
kvision
kweb
lambdaworld_cadiz
lanark
language-evolution
language-proposals
latvia
leakcanary
leedskotlinusergroup
lets-have-fun
libgdx
libkgd
library-development
lincheck
linkeddata
lithuania
london
losangeles
lottie
love
lychee
macedonia
machinelearningbawas
madrid
malaysia
mathematics
meetkotlin
memes
meta
metro-detroit
mexico
miami
micronaut
minnesota
minutest
mirror
mockk
moko
moldova
monsterpuzzle
montreal
moonbean
morocco
motionlayout
mpapt
mu
multiplatform
mumbai
munich
mvikotlin
mvrx
myndocs-oauth2-server
naming
navigation-architecture-component
nepal
new-mexico
new-zealand
newname
nigeria
nodejs
norway
npm-publish
nyc
oceania
ohio-kotlin-users
oldenburg
oolong
opensource
orbit-mvi
osgi
otpisani
package-search
pakistan
panamá
pattern-matching
pbandk
pdx
peru
philippines
phoenix
pinoy
pocketgitclient
polish
popkorn
portugal
practical-functional-programming
proguard
prozis-android-backup
pyhsikal
python
python-contributors
quasar
random
re
react
reaktive
realm
realworldkotlin
reductor
reduks
redux
redux-kotlin
refactoring-to-kotlin
reflect
refreshversions
reports
result
rethink
revolver
rhein-main
rocksdb
romania
room
rpi-pico
rsocket
russian
russian_feed
russian-kotlinasfirst
rx
rxjava
san-diego
science
scotland
scrcast
scrimage
script
scripting
seattle
serialization
server
sg-user-group
singapore
skia-wasm-interop-temp
skrape-it
slovak
snake
sofl-user-group
southafrica
spacemacs
spain
spanish
speaking
spek
spin
splitties
spotify-mobius
spring
spring-security
squarelibraries
stackoverflow
stacks
stayhungrystayfoolish
stdlib
stlouis
strife-discord-lib
strikt
students
stuttgart
sudan
swagger-gradle-codegen
swarm
sweden
swing
swiss-user-group
switzerland
talking-kotlin
tallinn
tampa
teamcity
tegal
tempe
tensorflow
terminal
test
testing
testtestest
texas
tgbotapi
thailand
tornadofx
touchlab-tools
training
tricity-kotlin-user-group
trójmiasto
truth
tunisia
turkey
turkiye
twitter-feed
uae
udacityindia
uk
ukrainian
uniflow
unkonf
uruguay
utah
uuid
vancouver
vankotlin
vertx
videos
vienna
vietnam
vim
vkug
vuejs
web-mpp
webassembly
webrtc
wimix_sentry
wwdc
zircon
Powered by
Title
t

Timo Drick

01/27/2021, 11:20 AM
In compose version 0.3.0-build143 the onDispose function is replaced by DisposableEffect where a key is required. But in my use case i just want to do some cleanups when the composable is removed from the view tree. How can i implement this with the new API?
j

jim

01/27/2021, 11:24 AM
Can you elaborate on the type of cleanup you want to perform? It is our expectation that a
DisposableEffect
without a key would be rare, and would love to see details about any counterexample. With regards to your specific question though, I believe you can just pass in
Unit
as the key parameter, which will satisfy the compiler.
The fact that passing
Unit
looks awkward is very intentional, goal is to get a code reviewer to be like 😬 (and hopefully ask questions) when they see it.
t

Timo Drick

01/27/2021, 11:28 AM
I do have a custom navigation framework. And a composable is used as root element for the navigation. Than when the app navigates to different screens a backstack is build up. When the root composable is disposed i want to reset the backstack.
btw i also use onCommit(key) in my app without needs for a dispose function. Do i have to use DisposableEffect with an empty onDispose implementation? Or is there any other alternative?
a

Adam Powell

01/27/2021, 3:11 PM
For the first one, it sounds like the back stack object being reset on disposal is an appropriate key
for onCommit, it depends on what you're doing with it. If you're applying changes to other objects, use
SideEffect
.
For these use cases you shouldn't need the key; compose shouldn't be responsible for idempotence of set operations on your objects, the objects themselves should do that.
t

Timo Drick

01/27/2021, 3:16 PM
I want to code a transition effect. So when the key changes i need to update the state of the transition object.
And i do not want to create a new Transition object because i need the old state
other wise i could use just remember with keys
Code is like this:
val ts = remember { CrosstransitionState<SavedStateData<T>>() }
DisposableEffect(transition) {
    ts.newTarget(transition.data)
    ...
    ts.scope?.invalidate()
    onDispose {

    }
}
a

Adam Powell

01/27/2021, 3:22 PM
seems like what you're looking for is:
val ts = remember { ... }
SideEffect {
  ts.target = transition.data
}
setting
target
should skip if the new value is equal or invalidate as necessary
t

Timo Drick

01/27/2021, 3:24 PM
Is the code inside SideEffect is executed again if the MutableState of the variable transition is changed?
a

Adam Powell

01/27/2021, 3:26 PM
It is executed only after the current recomposition succeeds
every time that composable is recomposed
t

Timo Drick

01/27/2021, 3:26 PM
Ok but than this code will not work.
a

Adam Powell

01/27/2021, 3:27 PM
If you were using the
onCommit
to observe a snapshot state object for changes to run some code when it does change, then you've encountered the antipattern that this API change was intended to break/make very awkward 🙂
the reason not to use
onCommit
that way is that it forces recomposition of its surroundings to dispatch an event callback, and it does so by waiting for a composition frame.
Chances are there's a 1-frame delay before your work actually starts that doesn't need to be there as a result too.
The way to think of this is that you want to independently observe changes to snapshot state, and make sure that those changes feed into later recomposition only if needed
t

Timo Drick

01/27/2021, 3:30 PM
Ok i see.
a

Adam Powell

01/27/2021, 3:31 PM
one way to do this is with `snapshotFlow`:
val ts = remember { ... }
LaunchedEffect(ts) {
  snapshotFlow { transition }.collect { newTransitionValue ->
    ts.newTarget(newTransitionValue.data)
    // ...
  }
}
this lets you observe changes independent of recomposition, but still manage the scope of that observation within your composable.
t

Timo Drick

01/27/2021, 3:32 PM
I think i do have this code snippets from older implementations of Crossfade or other transition effect.
a

Adam Powell

01/27/2021, 3:33 PM
probably 🙂 we learned many of the antipatterns and why they're antipatterns the hard way in our own codebase
not all of them have been addressed yet
t

Timo Drick

01/27/2021, 3:34 PM
Ok i think i could do it than this way:
val ts = remember { ... }
if (ts.target != transition.data) {
    ts.target = transition.data
}
this would recompose the composable when transition is changed. And this is exactly what i want.
In Crossfade it is also implemented like that
a

Adam Powell

01/27/2021, 3:37 PM
So long as `ts.target`'s set function has no other side effects beyond setting other snapshot state, that can work fine. If it does, you might be in for some correctness problems in the not too distant future, since composition can fail and you don't want lingering side effects that we can't roll back by discarding the current mutable snapshot in progress.
t

Timo Drick

01/27/2021, 3:44 PM
ok thx. I will try to fix my code 😄