Status Update
No update yet.
Comments
si...@google.com
si...@google.com
si...@google.com
ap...@google.com
just query LocalView instead of setting this metadata at the ComposeView layer to unblock the most common cases.
As we can't know when / if the ComposeView is moved to a different part of the View hierarchy, we don't have a good callback / place to update this value within ComposeView - theoretically since shouldDelayChildPressedState is a function, it could return different values at different points in time in any case. So we should instead continue to query the view hierarchy during a press, to see if at that point in time we should delay the press or not.
So instead we just need to provide whether there is a scrollable Compose node, and then consumers can combine querying that with whether there is a scrollable ViewGroup, to work out whether they should delay presses or not. AndroidView can solely query whether it is in a scrollable Compose node, as anything inside it will look up the view hierarchy anyway
Description
Forked from
I wonder if it is better to return an Object to the developer after the result of startInput. This way, we differentiate the currently used service that you can call, stop, updateState etc. Using integer increments for a service that can be used at any time is a little dangerous.