It seems like if I start an external activity (like the
Intent with a Uri) and then press back to come back to my compose-based app, the Composable parts aren't recomposed.The containing activity gets onStart and onResume called as expected. Does that mean I should be creating my app in onStart instead of onCreate?
Or is there a way to detect this from within composables? I'm expecting a state change upon returning to the app, based on something that happens in the activity's onStop when the app loses focus.Edit: Is the right way to use
? It seems like that works.
didn't work as well, seems like some weird race condition in my code.
2 years ago
Wouuuahhhh you can’t set
? Bold of Compose to fight directly the designers of the world 😂
text = "Save this dough recipe!",
style = TextStyle(fontSize = 16.dp) // doesn't compile
The compose compiler treats compose functions in much similar way the kotlin compiler does to suspend functions. Correct? My curiosity is, why did the Compose Dev team decide to go with annotations (i.e.
) instead of making compose a reserved word, similar to suspend functions?Knowing this was much influenced by JB, if the annotations approach seemed more convenient, why didn't they go with it for suspend functions? (i.e
2 years ago
Hi, Everyone I just started exploring Compose and coming from SwiftUI this feels at home, I tried looking for documentation on all the available API but could not find it, can someone please guide me to the Compose API docs (If they exist) ?