This field affects the rate of acceleration as the pointer is moved across the display. It is recommended that this field is never set manually, as the user will need to determine the best acceleration level through trial and error in the user preferences program.

This field is not relevant in a hosted environment.

If the pointer is anchored to a surface through SetCursor(), this field will refer to the surface that holds the anchor.

The pointer graphic can be changed to a custom image if the PTC::CUSTOM CursorID type is defined and an image is drawn to the Bitmap object referenced by this field.

This field defines the order of interpretation of the mouse buttons when they are pressed. This allows a right handed device to have its buttons remapped to mimic a left-handed device for instance.

The default button order is defined as 123456789AB. The left, right and middle mouse buttons are defined as 1, 2 and 3 respectively. The rest of the buttons are assigned by the device, preferably starting from the left of the device and moving clockwise.

It is legal for buttons to be referenced more than once, for instance a setting of 111 will force the middle and right mouse buttons to translate to the left mouse button.

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

This field returns the state of mouse input buttons as bit-flags, sorted by order of their importance. A bit flag of 1 indicates that the user is holding the button down. The bit order is LMB, RMB, MMB, with the LMB starting at bit position zero. Additional buttons are supported but their exact order will depend on the device that is in use, and the configuration of their order may be further customised by the user.

The ClickSlop value defines the allowable pixel distance between two clicks for them to be considered a double-click (or a drag operation if they exceed the distance).

If the pointer is currently owned by an object, this field will refer to that object ID. Pointer ownership is managed by the SetCursor() function.

A double-click is recognised when two separate clicks occur within a pre-determined time frame. The length of that time frame is determined in the DoubleClick field and is measured in seconds. The recommended interval is 0.3 seconds, although the user can store his own preference in the pointer configuration file.

When the pointer is in drag-mode, the custom item number that was defined in the initial call to StartCursorDrag() will be defined here. At all other times this field will be set to zero.

When the pointer is in drag-mode, the object that is managing the source data will be referenced in this field. At all other times this field will be set to zero.

Item dragging is managed by the StartCursorDrag() function.

By default a pointer will read its input directly from the mouse port. However it may be convenient for the pointer to receive its information from elsewhere, in which case you can set this field to point to a different input object. The object that you use must be able to send joyport information over data channels.

The maximum speed at which the pointer can move per frame is specified in this field. This field is provided to help the user for times where the pointer may be moving to fast (for example if the hardware driver is interpreting the mouse movement at larger offsets than what is normal). You can also set the value to 1 if a digital simulation is required.

This field returns a reference to the object directly under the pointer's hot-spot. NULL can be returned if there is no surface object under the pointer.

The OverX field provides other classes with a means of finding out exactly where the pointer is positioned over their display area. For example, if a user click occurs on an Image and it is necessary to find out what coordinates where affected, the OverX and OverY fields can be polled to determine the exact position of the user click.

The OverY field provides other classes with a means of finding out exactly where the pointer is positioned over their display area. For example, if a user click occurs on an Image and it is necessary to find out what coordinates where affected, the OverX and OverY fields can be polled to determine the exact position of the user click.

This special field applies to 3D interfaces only. It reflects the position of the pointer within 3-Dimensional displays, by returning its coordinate along the Z axis.

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

The speed at which the pointer moves can be adjusted with this field. To lower the speed, use a value between 0 and 100%. To increase the speed, use a value between 100 and 1000%. The speed of the pointer is complemented by the MaxSpeed field, which restricts the maximum amount of pixels that a pointer can move each time the input device is polled.

The surface that is directly under the pointer's hot spot is referenced by this field. It is automatically updated whenever the position of the pointer changes or a new surface appears under the pointer.

This field defines a multiplier that is applied to values coming from the mouse wheel. A setting of 1.0 leaves the wheel speed unaltered, while a setting of 2.0 would double the regular speed.