欧美区 亚洲区 图片区

DarkenTo explain again about dispatchTransformedTouchEvent (), there are two kinds of codes: and. Simply understood, the former is to call ViewGroup's own onTouchEvent () to consume, while the latter distributes events to sub-views (on the interface) for processing. If the child view is a ViewGroup, the process of handling events by the child view is similar to that of the parent view, starting from the DispatchTouchEvent () of the ViewGroup; If the child View is not a ViewGroup, the DispatchTouchEvent () logic of the View is directly executed. However, there is no code in View's dispatchTouchEvent () to pass the event to the parent View for consumption. In fact, the consumption process event is not passed, but whether to call its own onTouchEvent () is determined according to the return value of the child View's dispatchTouchEvent () and some ViewGroup's own records. Well, the idea is provided here.心情一放松，葫芦就觉得怀里的人儿好软。Referee Answer:四个水灵灵的小姑娘，被他分别取名叫白猫、黑猫、黄猫、花猫，号称四猫。Every ship should travel at a safe speed at all times so that appropriate and effective collision avoidance actions can be taken and the ship can be stopped within a distance suitable for the current environment and conditions. In determining the safe speed, the following factors shall be taken into account:It is easy to see that OvR only needs to train N classifiers, while OvO needs to train N (N-1)/2 classifiers, so the storage overhead and test time overhead of OvO are usually larger than OvR. However, in training, each classifier of OVR uses all training samples, while each classifier of OVO only uses samples of two classes. Therefore, when there are many classes, the training time cost of OVO is usually smaller than that of OVR. As for the prediction performance, it depends on the specific data distribution, which is similar in most cases.