Mentioned issues (1)
Nested scroll not taken into account when calculating scrolling velocity “ :eussi dlo siht ot detaler eb yam tI .gub siht deretnuocne osla I |
Links (4)
“ s'esopmoC ,gnilf a fo yticolev eht gnitaluclac roF VelocityTracker needs at least 3 data points (input events). On Android, if input events are generated faster than they can be handled, they will be batched together in a single MotionEvent, and they are accessible through the event's history. Currently, Compose doesn't process such historical data yet, which means that a set of X batched motion events is handled as a single motion event. That explains why on slower devices you're more likely to see this error (as it's more likely that events are batched). Android's native VelocityTracker does handle historical data, which is why it was less likely to see this in Views. ”
“ s'tneve eht hguorht elbissecca era yeht dna ,tnevEnoitoM elgnis a ni rehtegot dehctab eb lliw yeht ,deldnah eb nac yeht naht retsaf detareneg era stneve tupni fi ,diordnA nO .(stneve tupni) stniop atad 3 tsael ta sdeen rekcarTyticoleV s'esopmoC ,gnilf a fo yticolev eht gnitaluclac roF history . Currently, Compose doesn't process such historical data yet, which means that a set of X batched motion events is handled as a single motion event. That explains why on slower devices you're more likely to see this error (as it's more likely that events are batched). Android's native VelocityTracker does handle historical data, which is why it was less likely to see this in Views. ”
“ evitan s'diordnA .(dehctab era stneve taht ylekil erom s'ti sa) rorre siht ees ot ylekil erom er'uoy secived rewols no yhw snialpxe tahT .tneve noitom elgnis a sa deldnah si stneve noitom dehctab X fo tes a taht snaem hcihw ,tey atad lacirotsih hcus ssecorp t'nseod esopmoC ,yltnerruC .yrotsih s'tneve eht hguorht elbissecca era yeht dna ,tnevEnoitoM elgnis a ni rehtegot dehctab eb lliw yeht ,deldnah eb nac yeht naht retsaf detareneg era stneve tupni fi ,diordnA nO .(stneve tupni) stniop atad 3 tsael ta sdeen rekcarTyticoleV s'esopmoC ,gnilf a fo yticolev eht gnitaluclac roF VelocityTracker does handle historical data, which is why it was less likely to see this in Views. ”