forked from bartvdbraak/blender
75ab57efed
With edits by Campbell, thanks! Looks like in some cases (driver dependent?), `XDeviceMotionEvent` get generated with only part of expected data (e.g. only x coordinate, only pressure, etc.), data which did not change since last event being NULL. We know which data to actually handle with `XDeviceMotionEvent.first_axis` and `XDeviceMotionEvent.axes_count` values. Reviewed by: campbellbarton Differential Revision: https://developer.blender.org/D208 |
||
---|---|---|
.. | ||
doc | ||
intern | ||
test | ||
CMakeLists.txt | ||
GHOST_C-api.h | ||
GHOST_IEvent.h | ||
GHOST_IEventConsumer.h | ||
GHOST_ISystem.h | ||
GHOST_ISystemPaths.h | ||
GHOST_ITimerTask.h | ||
GHOST_IWindow.h | ||
GHOST_Path-api.h | ||
GHOST_Rect.h | ||
GHOST_Types.h | ||
SConscript |