Does Compose have a concept to explicitly ask for a recomposition? I am currently using some dummy state for that but that looks awkward.

Why do you need to trigger recomposition? Typically if this comes up there’s something else that’s probably wrong

What @Zach Klippenstein (he/him) [MOD] said. That said, if you still think you need it,

currentRecomposeScope()

will give you an object with an invalidate method on it

Well, I think I still need it. You have to consider that in the real world not all code is written from scratch and is not always written with Compose in mind. I have some code which encapsulates a lot of canvas drawing in a generic way and maintains its own state internally. I have however a callback which I can use to be notified about repaint requests and that leads me to the question of how to best hook this up with Compose.

True invalidation is fine, some people tend to use recomposition as a replacement for setting up a flow collector or other event-driven actor

That sounds a bit like what I am doing already right now and what looks ugly. If it does not exist yet, wouldn’t you think that introducing an explicit API for that purpose would make sense? (hint)