Android/frameworks_base
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Fix order of initialization arguments for obtained MotionEvents.

Browse Source 
Bug: 21330711
Change-Id: I308f7675d2730210228a0c01856616ce07d6374e
This commit is contained in:
Michael Wright
2015-06-10 14:57:33 +01:00
committed by The Android Automerger
parent ccdef2585a
commit c21f43d9fc
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
core/jni/android_view_MotionEvent.cpp
View File

@@ -370,7 +370,7 @@ static jlong android_view_MotionEvent_nativeInitialize(JNIEnv* env, jclass clazz
env->DeleteLocalRef(pointerCoordsObj);
}
event->initialize(deviceId, source, action, flags, edgeFlags, metaState, buttonState, 0,
event->initialize(deviceId, source, action, 0, flags, edgeFlags, metaState, buttonState,
xOffset, yOffset, xPrecision, yPrecision,
downTimeNanos, eventTimeNanos, pointerCount, pointerProperties, rawPointerCoords);