Post

Days since confusing myself with different frames of references and coordinate systems in Compose: 0

At minimum, you have a screen coordinate space (which is almost never what you want to use), a window coordinate space, and a Compose root coordinate space. Each of those can be measured in dps or pixels, and sometimes it matters if those pixels are integers or floats.

And then every single node has its own local coordinate space, after layouts and padding and scrolling and translations are each applied. Keeping track of what coordinate system you want to be working in is tricky when you start having complicated interactions that move across boundaries.

Mental translation between different coordinate spaces is tough. I somehow keep running into this problem in every other project. I wrote this while dealing with multiple windows in cascade: github.com/saket/cascad...

I guess value classes are the type-safety you're looking for?

You would need a different type for each frame of reference though I think - that'd work for the most important reference frames, but probably wouldn't scale well if you wanted to make sure two arbitrary composables were talking to each other properly.