Aura windows touch event problem

[Marshall Greenblatt]

Hi All,

I'm trying to debug a multi-touch issue with Windows 8. I'm currently testing with an external touch screen and I don't know if that's contributing to the problem or not. My Content API-based application creates a views::WebView [1] where the underlying Widget is parented to an application-provided HWND. I'm only receiving WM_TOUCH events for the upper-right corner of the content area (approx 500x500 pixels).

Using Spy++ I see that when I touch outside of the upper-right corner I get a WM_GESTURENOTIFY message [2] instead of a WM_TOUCH message. When I touch inside the upper-right corner I get a WM_TOUCH message [3] and HWNDMessageHandler::OnTouchEvent is called as expected. Rendering and mouse input events are otherwise correct across the entire content area and I've verified that the entire content area is "Chrome_WidgetWin_0".

This problem does not occur using Chome 22 or a recent nightly Chromium build. Any idea what might be causing it in my application?

Thanks,

Marshall

[1] https://code.google.com/p/chromiumembedded/source/browse/trunk/cef3/libcef/browser/browser_host_impl_win.cc#552

[2] Messages when touching outside the upper-right corner:

<00001> 001A0354 S WM_NCHITTEST xPos:-819 yPos:432

<00002> 001A0354 R WM_NCHITTEST nHittest:HTCLIENT

<00003> 001A0354 S WM_NCHITTEST xPos:-819 yPos:432

<00004> 001A0354 R WM_NCHITTEST nHittest:HTCLIENT

<00005> 001A0354 S message:0x024B [Unknown] wParam:0001013D lParam:001E0500

<00006> 001A0354 R message:0x024B [Unknown] lResult:FFFFFFFF

<00007> 001A0354 S WM_MOUSEACTIVATE hwndTopLevel:001E0500 nHittest:HTCLIENT uMsg:0246

<00008> 001A0354 R WM_MOUSEACTIVATE fuActivate:MA_ACTIVATE

<00009> 001A0354 P message:0x0249 [Unknown] wParam:6017013D lParam:0360F99A

<00010> 001A0354 P message:0x0246 [Unknown] wParam:6017013D lParam:0360F99A

<00011> 001A0354 S message:0x02CC [Unknown] wParam:00000000 lParam:0360F99A

<00012> 001A0354 R message:0x02CC [Unknown] lResult:00000000

<00013> 001A0354 S WM_GESTURENOTIFY

[2] Messages when touching inside the upper-right corner:

<00053> 001A0354 S WM_NCHITTEST xPos:-218 yPos:193

<00054> 001A0354 R WM_NCHITTEST nHittest:HTCLIENT

<00055> 001A0354 S WM_NCHITTEST xPos:-218 yPos:193

<00056> 001A0354 R WM_NCHITTEST nHittest:HTCLIENT

<00057> 001A0354 S message:0x024B [Unknown] wParam:0001013E lParam:001E0500

<00058> 001A0354 R message:0x024B [Unknown] lResult:FFFFFFFF

<00059> 001A0354 S WM_MOUSEACTIVATE hwndTopLevel:001E0500 nHittest:HTCLIENT uMsg:0246

<00060> 001A0354 R WM_MOUSEACTIVATE fuActivate:MA_ACTIVATE

<00061> 001A0354 P message:0x0249 [Unknown] wParam:6017013E lParam:0183FE4B

<00062> 001A0354 P message:0x0246 [Unknown] wParam:6017013E lParam:0183FE4B

<00063> 001A0354 S message:0x02CC [Unknown] wParam:00000000 lParam:0183FE4B

<00064> 001A0354 R message:0x02CC [Unknown] lResult:00000000

<00065> 001A0354 S WM_TOUCH

[Marshall Greenblatt]

On Thu, Feb 6, 2014 at 4:05 PM, Marshall Greenblatt <magree...@gmail.com> wrote:

Hi All,

I'm trying to debug a multi-touch issue with Windows 8. I'm currently testing with an external touch screen and I don't know if that's contributing to the problem or not.

The problem seems related to my Windows display settings (Control Panel\Appearance and Personalization\Display).

1. Set 200% zoom with the touch display as the secondary display. Drag the window to the secondary (touch) display. Get the incorrect behavior mentioned in the original email.

2. Set 200% zoom with the touch display as the primary display. Launch the window on the touch display. Don't get any WM_TOUCH messages.

3. Set 100% zoom with the touch display as the primary display. Launch the window on the touch display. Get WM_TOUCH messages for the whole client area as expected.

Is there some special handling that Chrome performs when moving between different displays?