HP Dx9000 Resources for Developing Touch-Friendly Applications for HP Business - Page 13

Touch Support in Windows 7

Page 13 highlights

HP recommends Windows Vista® Business msg.Result = (IntPtr)result; } break; default: base.WndProc(ref msg); break; } } Refer to the article, "Touch Input Support in Windows Vista," on MSDN for more details. Disabling System Gestures By default a window application receives all system gesture events. You may need to disable some system gesture events by responding to WM_TABLET_QUERYSYSTEMGESTURESTATUS message in your window procedure. Refer to the article, "WM_TABLET_QUERYSYSTEMGESTURESTATUS Message Message," on MSDN for more details: Additional advanced touch input manipulation is available on MSDN at http://msdn.microsoft.com/. Touch Support in Windows 7® Windows 7 provides a richer support for the development of touch applications. Support includes:  The default behavior for many gestures that touch-unaware applications automatically receive  Gesture messages (WM_GESTURE) to get gestures performed by users  Touch input messages (WM_TOUCH) to get information about specific contact points  Manipulation APIs (using manipulation processor and inertia processor) on top of touch input messages to get actions performed by users as well as how actions can be interpreted An application can receive either gesture messages or touch input messages but not both at the same time. By default, Windows sends WM_GESTURE notifications to an application. If the application does not handle these events, they are bubbled up and Windows will send back equivalent legacy messages like mouse left button click, mouse left double click, mouse right button up, mouse right button down, etc. Consequently, that is why touch-unaware applications can still get good touch support. Not all gestures have equivalent legacy messages. To provide a better touch user experience, you may need to handle gesture messages that have no legacy 13

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37

HP recommends Windows Vista® Business
13
msg.Result = (IntPtr)result;
}
break;
default:
base.WndProc(ref msg);
break;
}
}
Refer to the article
, “
Touch Input Support in Windows Vista
,
on MSDN for more
details.
Disabling System Gestures
By default a window application receives all system gesture events. You may need
to disable some system gesture events by responding to
WM_TABLET_QUERYSYSTEMGESTURESTATUS message in your window procedure.
Refer to the article,
WM_TABLET_QUERYSYSTEMGESTURESTATUS Message
Message
,”
on MSDN for more details:
Additional advanced touch input manipulation is available on MSDN at
.
Touch Support in Windows 7
®
Windows 7 provides a richer support for the development of touch applications.
Support includes:
The default behavior for many gestures that touch-unaware applications
automatically receive
Gesture messages (WM_GESTURE) to get gestures performed by users
Touch input messages (WM_TOUCH) to get information about specific contact
points
Manipulation APIs (using manipulation processor and inertia processor) on top
of touch input messages to get actions performed by users as well as how
actions can be interpreted
An application can receive either gesture messages or touch input messages but not
both at the same time. By default, Windows sends WM_GESTURE notifications to
an application. If the application does not handle these events, they are bubbled
up and Windows will send back equivalent legacy messages like mouse left button
click, mouse left double click, mouse right button up, mouse right button down, etc.
Consequently, that is why touch-unaware applications can still get good touch
support.
Not all gestures have equivalent legacy messages. To provide a better touch user
experience, you may need to handle gesture messages that have no legacy