This field affects relative pointer movement before the final coordinates are applied. It is normally treated as a user preference, because suitable acceleration values depend on the input device and user expectations.

Hosted display drivers may apply their own pointer acceleration before events reach the display module, so this field is not always relevant in hosted environments.

If the pointer has been anchored to a surface through SetCursor(), this field refers to the surface that receives anchored movement events.

The pointer graphic can be changed to a custom image by drawing into this Bitmap and selecting PTC::CUSTOM with SetCustomCursor().

This field defines how physical pointer buttons are mapped to logical button positions when pressed. It can be used to remap a right-handed device for left-handed use, or to normalise unusual button layouts.

The default button order is 123456789AB. The left, right and middle buttons are defined as 1, 2 and 3 respectively. Additional buttons are assigned by the device.

Buttons may be referenced more than once. For example, 111 maps the first three physical buttons to the logical left button.

Changes to this field will have an immediate impact on the pointing device's behaviour.

This field returns the current pointer button state as bit flags after ButtonOrder mapping has been applied. A set bit indicates that the corresponding logical button is being held down.

The first three bits represent left, right and middle button state respectively, with the left button at bit position zero. Additional buttons are supported, but their order depends on the device and the active ButtonOrder setting.

ClickSlop defines the allowed pointer movement, in pixels, before a press-and-release sequence is treated as a drag rather than a click. The same tolerance is used when deciding whether a second click is close enough to qualify as a double-click.

This field stores the cursor image currently selected for the pointer. Use SetCursor() or SetCustomCursor() to change the cursor after initialisation.

If the cursor is currently locked by an owner, this field refers to that owner's object ID. Cursor ownership is managed by SetCursor() and released with RestoreCursor().

A double-click is recognised when two presses of the same logical button occur within this interval. The value is measured in seconds and defaults to the user's pointer preference.

When a drag-and-drop operation is active, this field contains the custom item number supplied to StartCursorDrag(). At all other times it is zero.

When a drag-and-drop operation is active, this field refers to the object managing the source data. At all other times it is zero.

Item dragging is managed by StartCursorDrag().

This field records an alternate object intended to supply pointer movement. Input records delivered to the pointer must use the same DATA::DEVICE_INPUT format accepted by DataFeed().

This field limits the maximum relative movement applied to the pointer during a single update. Values assigned to the field are clamped to the supported range.

This field returns the object directly under the pointer hot spot. NULL can be returned if there is no surface object under the pointer.

This field gives the horizontal position of the pointer hot spot relative to OverObject. It can be read when handling input to determine the object-local coordinate affected by a click, wheel or movement event.

This field gives the vertical position of the pointer hot spot relative to OverObject. It can be read together with OverX to determine the object-local coordinate affected by pointer input.

This field is reserved for interfaces that can report pointer depth. It reflects the pointer coordinate on the Z axis relative to the object under the hot spot.

If the pointer has been restricted to a surface through SetCursor(), this field refers to that surface. If the pointer is not restricted, this field is zero.

This field controls the relative movement multiplier, expressed as a percentage. Values below 100 reduce movement, while values above 100 increase movement. MaxSpeed is applied as a separate upper limit.

This field refers to the top-most Surface under the pointer hot spot. It is automatically updated when the pointer moves or when surface visibility, position or stacking changes affect the object under the pointer.

This field defines a multiplier applied to pointer wheel values. A setting of 1.0 leaves wheel input unchanged, while 2.0 doubles the reported value.

Setting X or Y on an initialised pointer forwards the change through MoveToPoint().