HI!

On Thu, Sep 2, 2010 at 3:20 PM, Nitin Mahajan <[email protected]> wrote:

> Here is logcat output
>
> : *** set_screen_state 1
> V/WindowManager(  845): dispatchPointer MotionEvent{43caf818 action=2
> x=722.0 y=484.0 pressure=0.0 size=0.0}
> I/KeyInputQueue(  845): rel event found, class :64 mouse value: 64
> I/KeyInputQueue(  845): rel event found, class :64 mouse value: 64
> V/KeyInputQueue(  845): Absolute: x=233 y=149 ev=MotionEvent{43caf818
> action=2 x=233.0 y=149.0 pressure=0.0 size=0.0}
> I/KeyInputQueue(  845): Enqueueing: MotionEvent{43caf818 action=2 x=233.0
> y=149.0 pressure=0.0 size=0.0}
> I/power   (  845): *** set_screen_state 1
> V/WindowManager(  845): dispatchPointer MotionEvent{43caf818 action=2
> x=722.0 y=484.0 pressure=0.0 size=0.0}
> I/KeyInputQueue(  845): rel event found, class :64 mouse value: 64
> I/KeyInputQueue(  845): rel event found, class :64 mouse value: 64
> V/KeyInputQueue(  845): Absolute: x=237 y=152 ev=MotionEvent{43caf818
> action=2 x=237.0 y=152.0 pressure=0.0 size=0.0}
> I/KeyInputQueue(  845): Enqueueing: MotionEvent{43caf818 action=2 x=237.0
> y=152.0 pressure=0.0 size=0.0}
> I/power   (  845): *** set_screen_state 1
> V/WindowManager(  845): dispatchPointer MotionEvent{43caf818 action=2
> x=722.0 y=484.0 pressure=0.0 size=0.0}
> I/KeyInputQueue(  845): rel event found, class :64 mouse value: 64
> V/KeyInputQueue(  845): Absolute: x=240 y=152 ev=MotionEvent{43caf818
> action=2 x=240.0 y=152.0 pressure=0.0 size=0.0}
> I/KeyInputQueue(  845): Enqueueing: MotionEvent{43caf818 action=2 x=240.0
> y=152.0 pressure=0.0 size=0.0}
> I/power   (  845): *** set_screen_state 1
> V/WindowManager(  845): dispatchPointer MotionEvent{43caf818 action=2
> x=722.0 y=484.0 pressure=0.0 size=0.0}
> I/KeyInputQueue(  845): rel event found, class :64 mouse value: 64
> I/KeyInputQueue(  845): rel event found, class :64 mouse value: 64
> V/KeyInputQueue(  845): Absolute: x=242 y=154 ev=MotionEvent{43caf818
> action=2 x=242.0 y=154.0 pressure=0.0 size=0.0}
> I/KeyInputQueue(  845): Enqueueing: MotionEvent{43caf818 action=2 x=242.0
> y=154.0 pressure=0.0 size=0.0}
> I/power   (  845): *** set_screen_state 1
> V/WindowManager(  845): dispatchPointer MotionEvent{43caf818 action=2
> x=722.0 y=484.0 pressure=0.0 size=0.0}
> I/KeyInputQueue(  845): rel event found, class :64 mouse value: 64
> V/KeyInputQueue(  845): Absolute: x=244 y=154 ev=MotionEvent{43caf818
> action=2 x=244.0 y=154.0 pressure=0.0 size=0.0}
> I/KeyInputQueue(  845): Enqueueing: MotionEvent{43caf818 action=2 x=244.0
> y=154.0 pressure=0.0 size=0.0}
> I/power   (  845): ***
> set_screen_state 1
> V/WindowManager(  845): dispatchPointer MotionEvent{43caf818 action=2
> x=722.0 y=484.0 pressure=0.0 size=0.0}
> I/power   (  845): *** set_screen_state 1
> I/power   (  845): *** set_screen_state 1
> D/dalvikvm(  915): GC_FOR_MALLOC freed 5103 objects / 289456 bytes in 47ms
>
>
> regards
> -Nitin
>
>
I am able to see the cursor now, but mouse click does not work. Here is the
Logcat output per click.

# V/InputDevice(  852): Processing 1 pointers (going from 0 to 1) touch hack
false
I/InputDevice(  852): mouse action 0
I/KeyInputQueue(  852): Enqueueing: MotionEvent{43d34168 action=0 x=356.0
y=166.0 pressure=0.0 size=0.0}
V/WindowManager(  852): Event: type=64 data=MotionEvent{43d34168 action=0
x=356.0 y=166.0 pressure=0.0 size=0.0}
V/WindowManager(  852): dispatchPointer MotionEvent{43d34168 action=0
x=356.0 y=166.0 pressure=0.0 size=0.0}
V/WindowManager(  852): waitForLastKey: mFinished=true, mLastWin=null
V/WindowManager(  852): Skipping: null MotionEvent{43d34168 action=0 x=356.0
y=166.0 pressure=0.0 size=0.0}
W/WindowManager(  852): No window to dispatch pointer action 0
V/WindowManager(  852): Waiting for next key: now=1179099, repeat @ 10649273
V/InputDevice(  852): Processing 1 pointers (going from 1 to 2) touch hack
false
I/InputDevice(  852): mouse action 1
I/KeyInputQueue(  852): Enqueueing: MotionEvent{43d34168 action=1 x=356.0
y=166.0 pressure=0.0 size=0.0}
V/WindowManager(  852): Event: type=64 data=MotionEvent{43d34168 action=1
x=356.0 y=166.0 pressure=0.0 size=0.0}
V/WindowManager(  852): dispatchPointer MotionEvent{43d34168 action=1
x=356.0 y=166.0 pressure=0.0 size=0.0}
V/WindowManager(  852): waitForLastKey: mFinished=true, mLastWin=null
V/WindowManager(  852): Skipping: null MotionEvent{43d34168 action=1 x=356.0
y=166.0 pressure=0.0 size=0.0}
W/WindowManager(  852): No window to dispatch pointer action 1
V/WindowManager(  852): Waiting for next key: now=1179219, repeat @ 10649273

Can I get some hints?

thanks and regards
Nitin


>
> ---------- Forwarded message ----------
> From: Nitin Mahajan <[email protected]>
> Date: Thu, Sep 2, 2010 at 3:18 PM
> Subject: Mouse cursor:ssue with dispatchPointer
> To: [email protected]
>
>
> Hello,
>
> I have applied the mouse cursor patch for android-x86 from here
>
> http://git.android-x86.org/?p=platform/frameworks/base.git;a=commitdiff;h=41d38532eb9cc8a3bf6742abb344d86cd40639f1
>
> I am not able to see the mouse cursor, and I see these messages in Logcat
> while moving the mouse, which suggest that dispatchPointer() in
> WindowManagerService.java
> is always dispatching wrong co-ordinates which are out of screen (720 x
> 480), and hence cursor is not visible.
>
> Can I get some pointers to what might be going wrong?
>
> regards
> -Nitin
>
>
>
>

-- 
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting

Reply via email to