Making the View Interactive 视图互动
2013-04-20 15:21
260 查看
Drawing a UI is only one part of creating a custom view. You also need to make your view respond to user input in a way that closely resembles the real-world action you're mimicking. Objects should always act in the same way that real objects do. For example,
images should not immediately pop out of existence and reappear somewhere else, because objects in the real world don't do that. Instead, images should move from one place to another.
Users also sense subtle behavior or feel in an interface, and react best to subtleties that mimic the real world. For example, when users fling a UI object, they should sense friction at the beginning that delays the motion, and then at the end sense momentum
that carries the motion beyond the fling.
This lesson demonstrates how to use features of the Android framework to add these real-world behaviors to your custom view. http://blog.csdn.net/sergeycao
Android system is touch, which triggers
Touch events by themselves are not particularly useful. Modern touch UIs define interactions in terms of gestures such as tapping, pulling, pushing, flinging, and zooming. To convert raw touch events into gestures, Android provides
Construct a
Whether or not you use
When you pass
fling gesture, where the user quickly moves a finger across the screen and then lifts it. This gesture makes sense if the UI responds by moving quickly in the direction of the fling, then slowing down, as if the user had pushed on a flywheel and set
it spinning.
However, simulating the feel of a flywheel isn't trivial. A lot of physics and math are required to get a flywheel model working correctly. Fortunately, Android provides helper classes to simulate this and other behaviors. The
fling gestures.
To start a fling, call
Note: Although the velocity calculated by
The call to
Most views pass the
The
animation look smooth. There are two ways to do this:
Call
Set up a
The PieChart example uses the second approach. This technique is slightly more complex to set up, but it works more closely with the animation system and doesn't require potentially unnecessary view invalidation. The drawback is that
Note:
and omit the calls to the view animation system if the current level is less than 11.
property animation framework, introduced in Android 3.0, makes smooth transitions easy.
To use the animation system, whenever a property changes that will affect your view's appearance, do not change the property directly. Instead, use
If the value you want to change is one of the base
images should not immediately pop out of existence and reappear somewhere else, because objects in the real world don't do that. Instead, images should move from one place to another.
Users also sense subtle behavior or feel in an interface, and react best to subtleties that mimic the real world. For example, when users fling a UI object, they should sense friction at the beginning that delays the motion, and then at the end sense momentum
that carries the motion beyond the fling.
This lesson demonstrates how to use features of the Android framework to add these real-world behaviors to your custom view. http://blog.csdn.net/sergeycao
Handle Input Gestures
Like many other UI frameworks, Android supports an input event model. User actions are turned into events that trigger callbacks, and you can override the callbacks to customize how your application responds to the user. The most common input event in theAndroid system is touch, which triggers
onTouchEvent(android.view.MotionEvent). Override this method to handle the event:
@Override public boolean onTouchEvent(MotionEvent event) { return super.onTouchEvent(event); }
Touch events by themselves are not particularly useful. Modern touch UIs define interactions in terms of gestures such as tapping, pulling, pushing, flinging, and zooming. To convert raw touch events into gestures, Android provides
GestureDetector.
Construct a
GestureDetectorby passing in an instance of a class that implements
GestureDetector.OnGestureListener. If you only want to process a few gestures, you can extend
GestureDetector.SimpleOnGestureListenerinstead of implementing the
GestureDetector.OnGestureListenerinterface. For instance, this code creates a class that extends
GestureDetector.SimpleOnGestureListenerand overrides
onDown(MotionEvent).
class mListener extends GestureDetector.SimpleOnGestureListener { @Override public boolean onDown(MotionEvent e) { return true; } } mDetector = new GestureDetector(PieChart.this.getContext(), new mListener());
Whether or not you use
GestureDetector.SimpleOnGestureListener, you must always implement an
onDown()method that returns
true. This step is necessary because all gestures begin with an
onDown()message. If you return
falsefrom
onDown(), as
GestureDetector.SimpleOnGestureListenerdoes, the system assumes that you want to ignore the rest of the gesture, and the other methods of
GestureDetector.OnGestureListenernever get called. The only time you should return
falsefrom
onDown()is if you truly want to ignore an entire gesture. Once you've implemented
GestureDetector.OnGestureListenerand created an instance of
GestureDetector, you can use your
GestureDetectorto interpret the touch events you receive in
onTouchEvent().
@Override public boolean onTouchEvent(MotionEvent event) { boolean result = mDetector.onTouchEvent(event); if (!result) { if (event.getAction() == MotionEvent.ACTION_UP) { stopScrolling(); result = true; } } return result; }
When you pass
onTouchEvent()a touch event that it doesn't recognize as part of a gesture, it returns
false. You can then run your own custom gesture-detection code.
Create Physically Plausible Motion
Gestures are a powerful way to control touchscreen devices, but they can be counterintuitive and difficult to remember unless they produce physically plausible results. A good example of this is thefling gesture, where the user quickly moves a finger across the screen and then lifts it. This gesture makes sense if the UI responds by moving quickly in the direction of the fling, then slowing down, as if the user had pushed on a flywheel and set
it spinning.
However, simulating the feel of a flywheel isn't trivial. A lot of physics and math are required to get a flywheel model working correctly. Fortunately, Android provides helper classes to simulate this and other behaviors. The
Scrollerclass is the basis for handling flywheel-style
fling gestures.
To start a fling, call
fling()with the starting velocity and the minimum and maximum x and y values of the fling. For the velocity value, you can use the value computed for you by
GestureDetector.
@Override public boolean onFling(MotionEvent e1, MotionEvent e2, float velocityX, float velocityY) { mScroller.fling(currentX, currentY, velocityX / SCALE, velocityY / SCALE, minX, minY, maxX, maxY); postInvalidate(); }
Note: Although the velocity calculated by
GestureDetectoris physically accurate, many developers feel that using this value makes the fling animation too fast. It's common to divide the x and y velocity by a factor of 4 to 8.
The call to
fling()sets up the physics model for the fling gesture. Afterwards, you need to update the
Scrollerby calling
Scroller.computeScrollOffset()at regular intervals.
computeScrollOffset()updates the
Scrollerobject's internal state by reading the current time and using the physics model to calculate the x and y position at that time. Call
getCurrX()and
getCurrY()to retrieve these values.
Most views pass the
Scrollerobject's x and y position directly to
scrollTo(). The PieChart example is a little different: it uses the current scroll y position to set the rotational angle of the chart.
if (!mScroller.isFinished()) { mScroller.computeScrollOffset(); setPieRotation(mScroller.getCurrY()); }
The
Scrollerclass computes scroll positions for you, but it does not automatically apply those positions to your view. It's your responsibility to make sure you get and apply new coordinates often enough to make the scrolling
animation look smooth. There are two ways to do this:
Call
postInvalidate()after calling
fling(), in order to force a redraw. This technique requires that you compute scroll offsets in
onDraw()and call
postInvalidate()every time the scroll offset changes.
Set up a
ValueAnimatorto animate for the duration of the fling, and add a listener to process animation updates by calling
addUpdateListener().
The PieChart example uses the second approach. This technique is slightly more complex to set up, but it works more closely with the animation system and doesn't require potentially unnecessary view invalidation. The drawback is that
ValueAnimatoris not available prior to API level 11, so this technique cannot be used on devices running Android versions lower than 3.0.
Note:
ValueAnimatorisn't available prior to API level 11, but you can still use it in applications that target lower API levels. You just need to make sure to check the current API level at runtime,
and omit the calls to the view animation system if the current level is less than 11.
mScroller = new Scroller(getContext(), null, true); mScrollAnimator = ValueAnimator.ofFloat(0,1); mScrollAnimator.addUpdateListener(new ValueAnimator.AnimatorUpdateListener() { @Override public void onAnimationUpdate(ValueAnimator valueAnimator) { if (!mScroller.isFinished()) { mScroller.computeScrollOffset(); setPieRotation(mScroller.getCurrY()); } else { mScrollAnimator.cancel(); onScrollFinished(); } } });
Make Your Transitions Smooth
Users expect a modern UI to transition smoothly between states. UI elements fade in and out instead of appearing and disappearing. Motions begin and end smoothly instead of starting and stopping abruptly. The Androidproperty animation framework, introduced in Android 3.0, makes smooth transitions easy.
To use the animation system, whenever a property changes that will affect your view's appearance, do not change the property directly. Instead, use
ValueAnimatorto make the change. In the following example, modifying the currently selected pie slice in PieChart causes the entire chart to rotate so that the selection pointer is centered in the selected slice.
ValueAnimatorchanges the rotation over a period of several hundred milliseconds, rather than immediately setting the new rotation value.
mAutoCenterAnimator = ObjectAnimator.ofInt(PieChart.this, "PieRotation", 0); mAutoCenterAnimator.setIntValues(targetAngle); mAutoCenterAnimator.setDuration(AUTOCENTER_ANIM_DURATION); mAutoCenterAnimator.start();
If the value you want to change is one of the base
Viewproperties, doing the animation is even easier, because Views have a built-in
ViewPropertyAnimatorthat is optimized for simultaneous animation of multiple properties. For example:
animate().rotation(targetAngle).setDuration(ANIM_DURATION).start();
相关文章推荐
- android自定义view之(三) Making the View Interactive
- android自定义View_2——Making the View Interactive
- 对话框子视图Android自定义Dialog二次调用报错解决方法:The specified child already has a parent. You must call removeView()-java教程
- QT图形视图框架(The Graphics View Framework)
- Eclipse选项卡式的属性视图(The Eclipse Tabbed Properties View)
- 图形视图框架(The QGraphics View Framework 翻译)
- QT图形视图框架(The Graphics View Framework in QT)
- ios6.0之后单个屏幕旋转,不用根视图以及Application windows are expected to have a root view controller at the end of
- 图形视图框架(The QGraphics View Framework)(转)
- 转载:QT图形视图框架(The Graphics View Framework)
- mysql 创建视图出现1349 View's SELECT contains a subquery in the FROM clause解决办法
- MyEclipse Servers视图中提示 Could not create the view: An unexpected exception was thrown
- 图形视图框架(The QGraphics View Framework)(转)
- QT图形视图框架(The Graphics View Framework)
- 转载:QT图形视图框架(The Graphics View Framework)
- mysql 创建视图时提示View's SELECT contains a subquery in the FROM clause
- 【转载】10.1\t使用项目视图类(Using the Item View Convenience Classes)
- Optimizing the View 优化视图
- 【转载】10.1\t使用项目视图类(Using the Item View Convenience Classes)
- 图形视图框架(The QGraphics View Framework)