this is just a simulator !!!!!
Ii. Differences between a real machine and a simulator:
When it comes to our small users (when it comes to users, I think of the classic line of "My name is Mt" from the dark night man: Dear customer, I am a tender Dad !) Back to the topic: when our users are playing our games, especially RPG, they must press our virtual buttons on the touch screen for a long time, for example, we will draw a virtual steering wheel on
Analysis of Android multi-touch MultiTouchStatement:
The following describes how to use the application layer to support multi-touch operations and the onTouchEvent () method for conventional control touch operations. At the same time, I have some knowledge about the parameter MotionEvent OF THE onTouchEvent method.
B
Android's touch event-handling mechanism is more complex, especially after multiple touches and event interception are considered.
Android Touch event processing is divided into 3 levels: Activity layer, ViewGroup layer, view layer.
First of all, a few basic rules of touch event processing.
If the Action_down event is
Android -- View, ViewGroup event (Touch event) processing mechanism Summary, androidviewgroupEvents in Android
Touch event, four statuses:
ACTION_DOWN --> indicates that an event starts from ACTION_DOWN when the screen is pressed.ACTION_MOVE --> indicates a mobile gesture.ACTION_UP --> indicates leaving the screenACT
Get the multi-Touch point core code:Get the number and position of touch pointspublic boolean OnTouch (View V, motionevent event) {switch (event. Getaction()) {case Motionevent. ACTION_down:system. out. println("Down"); Break;Case Motionevent. ACTION_up:system. out. println("Number of touch points:"+event. Getpointercount());System. out. print
Android Touch event transfer mechanism: androidtouch
Respect Original: http://blog.csdn.net/yuanzeyao/article/details/38025165
Resource download: http://download.csdn.net/detail/yuanzeyao2008/7660997
In the previous article, I mainly explained the Touch event transfer process in the Android source code. Now I want to
The standard valid and touchable UI elements specified by Android4.0 are 48dp, which is converted to a physical size of about 9mm. The recommended target size is 7 ~ 10mm, which is consistent with the iPhone, is an area where the user's fingers are accurate and comfortable to touch. As shown in, your UI elements may be smaller than 48dp, the icons only have 32dp, And the buttons only have 40dp, but their actual operational focus has reached the 48dp s
I visited the Forum and accidentally saw a very good post, which is reproduced as follows:
Opening Speech: Recently, the program has made a small effect, and it needs to use touch. As a result, it is completely confused in the cloud. It just takes a good look at the android touch mechanism ..
Each subclass of viewgroup in An
onTouchListener interface of the View. When the View is bound with an onTouchListener, The onTouch method is called when a touch event is triggered.
OnTouchEvent method: override the method in Activity.
Android Touch event processing has three layers: Activity layer, ViewGroup layer, and View layer.Several Basic Principles of
Android ViewGroup touch event Transfer MechanismIntroduction
In the previous blog, we learned about the Android View touch event transfer mechanism. If you are not familiar with it, you can View the Android View touch event transf
Reprint Please specify source: http://blog.csdn.net/yyh352091626/article/details/68962736
Shortcut concept
Specific implementation
Buildconfig Configuration
Static configuration
Dynamic configuration
Create
Remove or disable
Update
return stack problem
Shortcut conceptShortcut is a new shortcut component for iOS-like features in
Reprint Please specify source: http://blog.csdn.net/yyh352091626/article/details/68962736
Shortcut concept
Detailed implementation
Buildconfig Configuration
Static configuration
Dynamic configuration
Create
Remove or disable
Update
return stack problem
Shortcut conceptShortcut is a shortcut component for the new iOS-like feature of
Android Touch event Transfer Mechanism
In the previous article, I mainly explained the Touch event transfer process in the Android source code. Now I want to use a demo and an instance to learn about the Touch event handling process in Andorid.In the
Gesturedetector convinced that the user after the first touch of the screen, not immediately following the second touch screen, that is, not "double-click" When the triggerTip://distanceX,是前后两次call的X距离,不是e2与e1的水平距离; 是前后两次call的Y距离,不是e2与e1的垂直距离How to use:1: Inheritance Gesturedetector.ongesturelistener2: Instantiation Detector Gesturedetector mdetector = new Gesturedetector (viewactivity.this, this);3: Callb
When I first started learning Android, I felt that Google's documents were not good, and when we studied gestures, I felt that Google's documents were too poor. A lot of constants, properties, and methods don't even have a description. There is no description, but there are so many gestures in ongesturelistener, it does not have a description, who can understand onlongpress and onshowpress before they try.Is there a difference between onscroll and onf
In this example, a simple Integer Calculator applies multi-touch operations: One Touch operation is addition operations, two touch operations are subtraction operations, three touch operations are multiplication operations, and four touch operations are Division operations.
(Mperformclick = = null) {Mperformclck = new Peformclick ();
} if (!post (Mperformclick)) {PerformClick ();
}
}
}
. . .
}
Break }
..
.
return true; }
As you can know from the above code, the Long_clickable property defaults to false as long as the clickable and long_clickable properties of the view are true (the clickable property of the view and the specific view. Setoncliklistener and Setonlongclicklistener automatically set the above
TouchEvent
TouchEvent three types of events: down, move, up.Where the move event is in one operation (one of the actions described here is that the user interacts with the screen, that is, the action sequence from down to up) may occur more than once.However, we think that an action sequence will contain the above three events, therefore, in the event processing is to deal with this process, and most importantly, the down event, which is the beginning of an action sequence, there is no down
The previous article mainly describes the TouchEvent distribution process of Android. There are two important functions: onInterceptTouchEvent and onTouchEvent. These two functions can be reinstalled to complete specific logic. OnInterceptTouchEvent is defined in ViewGroup. The default return value is false, indicating that TouchEvent is not intercepted. OnTouchEvent is defined in View. When ViewGroup calls onTouchEvent, super. onTouchEvent is used. B
The content source of this page is from Internet, which doesn't represent Alibaba Cloud's opinion;
products and services mentioned on that page don't have any relationship with Alibaba Cloud. If the
content of the page makes you feel confusing, please write us an email, we will handle the problem
within 5 days after receiving your email.
If you find any instances of plagiarism from the community, please send an email to:
info-contact@alibabacloud.com
and provide relevant evidence. A staff member will contact you within 5 working days.