Hej Thomas, thanks a lot for this write-up, really helped me out a lot! I just updated to v0.4.0 and I feel that the new Window and Dialog composables (with state parameter) break the above code. It worked fine in v0.4.0-build209 which I was using before.
I browsed a bit through the new code and found that those composables provide a WindowScope or DialogScope to the content composable. These contain a window or dialog field, which in turn give us a contentPane. So with a small change to the above code, we can attach to a Window or Dialog's dropTarget like this:
Hej Thomas, thanks a lot for this write-up, really helped me out a lot! I just updated to
v0.4.0
and I feel that the newWindow
andDialog
composables (withstate
parameter) break the above code. It worked fine inv0.4.0-build209
which I was using before.I browsed a bit through the new code and found that those composables provide a
WindowScope
orDialogScope
to the content composable. These contain awindow
ordialog
field, which in turn give us acontentPane
. So with a small change to the above code, we can attach to aWindow
orDialog
'sdropTarget
like this:Hope that helps someone :)
Awesome. Thanks for bringing this up. Maybe I should do some sort of follow-up to the series. Thanks. 👍