mirror of
https://github.com/flutter/flutter
synced 2024-10-13 11:42:54 +00:00
29898812d4
Currently the framework uses fairly large "hit slop" values to disambiguate taps from drags/pans. This makes sense on touch devices where the interaction is not very precise, on mice however it can feel as if the UI is lagging. This is immediately noticeable on our infra dashboard, where it takes almost half of a grid square of drag before the actual drag kicks in. One potential solution is to always use smaller constants depending on whether the interaction is mouse or touch based. The only reasonable choice is to use the pointer device kind and not target platform - same platform can have different input sources. This requires exposing the pointer device kind in a few new places in several of the gesture detectors, and using the enum to compute the correct hit slop from an expanded set of constants. This almost works, however there are a few places (notably ListViews) which uses the touch hit slop as a default value in scroll physics. It does not seem like it will be easy to disambiguate a user provided scroll physics constant from the default and/or adjust it somehow - this might require significant changes to scroll physics which I have left out of this PR. This PR does not adjust: kTouchSlop used in scroll_physics.dart's minFlingDistance kTouchSlop used in PrimaryPointerGestureRecognizer/LongPressGestureRecognizer |
||
|---|---|---|
| .. | ||
| automated_tests | ||
| benchmarks | ||
| bots | ||
| ci | ||
| customer_testing | ||
| devicelab | ||
| docs | ||
| integration_tests | ||
| manual_tests | ||
| missing_dependency_tests | ||
| snippets | ||
| tools | ||
| tracing_tests | ||
| prod_builders.json | ||
| README.md | ||
| try_builders.json | ||
This directory contains tools and resources that the Flutter team uses during the development of the framework. The tools in this directory should not be necessary for developing Flutter applications, though of course, they may be interesting if you are curious.
The tests in this directory are run in the framework_tests_misc-*
shards.
Luci builder file
try_builders.json and prod_builders.json contain the supported luci
try/prod builders for flutter.
try_builders.json
It follows format:
{
"builders":[
{
"name":"yyy",
"repo":"flutter",
"taskName":"zzz",
"enabled":true,
"run_if":["a/b/", "c/d/**"]
}
]
}
- enabled(optional):
trueis the default value if unspecified - run_if(optional): will always be triggered if unspecified
prod_builders.json
It follows format:
{
"builders":[
{
"name":"yyy",
"repo":"flutter",
"taskName":"zzz",
"flaky":false
}
]
}
try_builders.json will be mainly used in
flutter/cocoon to trigger/update pre-submit
flutter luci tasks, whereas prod_builders.json will be mainly used in flutter/cocoon
to refresh luci task statuses to dashboard.