In GEISv2, the "gesture name" does not make any sense, since a gesture frame may be classified in one or more ways. If you wish to see if a gesture frame belongs to a specific class, you need to use the geis_frame_is_class() call.
The documentation regarding GEIS_GESTURE_ATTRIBUTE_GESTURE_NAME reads as follows.
This attribute is filled only when using GEIS v1 API (the simplified
interface). On GEIS v2 this attribute has been replaced by the concept of
gesture classes. Use geis_frame_is_class() instead.
Regarding the number of touches and the et cetera (which is what, exactly?), could you please use the evemu-record tool from the utouch-evemu-tools package to capture the gesture performed on your input device that is causing the problem, and also use the evemu-describe tool from the same package to capture a device description of your device. Please attach both the description file and the recording file to this bug.
In GEISv2, the "gesture name" does not make any sense, since a gesture frame may be classified in one or more ways. If you wish to see if a gesture frame belongs to a specific class, you need to use the geis_frame_ is_class( ) call.
The documentation regarding GEIS_GESTURE_ ATTRIBUTE_ GESTURE_ NAME reads as follows.
This attribute is filled only when using GEIS v1 API (the simplified is_class( ) instead.
interface). On GEIS v2 this attribute has been replaced by the concept of
gesture classes. Use geis_frame_
Regarding the number of touches and the et cetera (which is what, exactly?), could you please use the evemu-record tool from the utouch-evemu-tools package to capture the gesture performed on your input device that is causing the problem, and also use the evemu-describe tool from the same package to capture a device description of your device. Please attach both the description file and the recording file to this bug.