Variant:
In response to multiple pointer movements, an input driver generates -a pointer event for each touch. The Window Server changes and delivers -the pointer events to the client application, as shown in the following -diagram.
Pointer-related events move from
-the driver to the application. The
The following terms -are introduced here and are used throughout the advanced pointer documentation:
A device that points at the screen, for example, a mouse, pen, -finger, or touchpad.
Handling more than one pointer at the same time.
Proximity in this context means the distance of the pointer -from the mobile device. Sensors detect the value of the proximity -of the pointer from the mobile device.
Pressure in this context is a value that indicates the force -applied to the mobile device by the pointer. Sensors detect the value -of the pressure of the pointer on the mobile device.
A logical -model is used to handle all of the different pointing devices correctly. -In this logical model, the pointer is performing an action when -any of the following scenarios occur:
An
An
Pointing devices can be in one of the following states:
The mapping between these states and physical actions -performed by the user vary for different pointing device types (mouse, -finger) and different phone models. Here are two example interpretations -of physical pointing device states:
Mouse. An example interpretation by a driver of the physical state of -a mouse is as follows: It is always in the up state except -when the left button is pressed, when it is in the down state. -It is never out of range.
Fingers -with proximity support. The following is an example interpretation -of finger physical states when the device has proximity support (that -is, it can measure the finger's proximity from the screen):
Out of range when proximity > 10cm
Up when -1cm < proximity <= 10cm
Down when proximity <= 1cm
In this way the finger can perform actions (for example, -press buttons, drag items) without touching the screen.
The system handles multiple
-pointers at the same time by identifying each one with a number and
-sending pointer events separately for each of them. A field (
On each phone there is a pool of available
-pointer numbers, ranging from 0 to
The pressure of
-the pointer on the screen is represented as a positive integer. The
-proximity of the pointer to the screen is represented as a negative
-integer. It is up to the UI Platform to define units of pressure and
-proximity, which may be non-linear. In the
If proximity -< 0 and pressure = 0 then the Z coordinate = proximity.
If proximity -= 0 and pressure >= 0 then the Z coordinate = pressure.
Enabling -many pointers for a window
Enables multiple pointers -to act on one window.
Enabling -concurrent control of many objects
Controls many objects -on one or more windows with many pointers.
Getting -z coordinates from TPointerEvent
Reads the pressure and -proximity values for a pointer.
Pinch zooming
Enables the user to zoom in and out of data by using two -fingers to pinch an area of the screen. Pinch zooming is normally -used in web-page, map, picture, chart and control applications.
Responding -to high pressure events
As the pointer state changes, -the pressure value can be checked. When it passes over a threshold -value, the Window Server responds appropriately to the client.
Variant:
In response to multiple pointer movements, an input driver generates +a pointer event for each touch. The Window Server changes and delivers +the pointer events to the client application, as shown in the following +diagram.
Pointer-related events move from the driver to the application.
+The
The following terms +are introduced here and are used throughout the advanced pointer documentation:
A device that points at the screen, for example, a mouse, pen, +finger, or touchpad.
Handling more than one pointer at the same time.
Proximity in this context means the distance of the pointer +from the mobile device. Sensors detect the value of the proximity +of the pointer from the mobile device.
Pressure in this context is a value that indicates the force +applied to the mobile device by the pointer. Sensors detect the value +of the pressure of the pointer on the mobile device.
A logical +model is used to handle all of the different pointing devices correctly. +In this logical model, the pointer is performing an action when +any of the following scenarios occur:
An
An
Pointing devices can be in one of the following states:
The mapping between these states and physical actions +performed by the user vary for different pointing device types (mouse, +finger) and different phone models. Here are two example interpretations +of physical pointing device states:
Mouse. An example interpretation by a driver of the physical state of +a mouse is as follows: It is always in the up state except +when the left button is pressed, when it is in the down state. +It is never out of range.
Fingers +with proximity support. The following is an example interpretation +of finger physical states when the device has proximity support (that +is, it can measure the finger's proximity from the screen):
Out of range when proximity > 10cm
Up when +1cm < proximity <= 10cm
Down when proximity <= 1cm
In this way the finger can perform actions (for example, +press buttons, drag items) without touching the screen.
The system handles multiple
+pointers at the same time by identifying each one with a number and
+sending pointer events separately for each of them. A field (
On each phone there is a pool
+of available pointer numbers, ranging from 0 to
The pressure of
+the pointer on the screen is represented as a positive integer. The
+proximity of the pointer to the screen is represented as a negative
+integer. It is up to the UI Platform to define units of pressure and
+proximity, which may be non-linear. In the
If proximity +< 0 and pressure = 0 then the Z coordinate = proximity.
If proximity += 0 and pressure >= 0 then the Z coordinate = pressure.
Enabling +many pointers for a window
Enables multiple pointers +to act on one window.
Enabling +concurrent control of many objects
Controls many objects +on one or more windows with many pointers.
Getting +z coordinates from TPointerEvent
Reads the pressure and +proximity values for a pointer.
Pinch zooming
Enables the user to zoom in and out of data by using two +fingers to pinch an area of the screen. Pinch zooming is normally +used in web-page, map, picture, chart and control applications.
Responding +to high pressure events
As the pointer state changes, +the pressure value can be checked. When it passes over a threshold +value, the Window Server responds appropriately to the client.