Follow-up Comment #4, bug #18692 (project mypaint):
No I think the min/max values are stored just to scale the actual input from
the device into the GTK range:
win32/gdkinput-win32.c- default:
win32/gdkinput-win32.c- axis_out[i] =
win32/gdkinput-win32.c- (gdkdev->info.axes[i].max *
(axis_data[i] - gdkdev->axes[i].min_value) +
win32/gdkinput-win32.c: gdkdev->info.axes[i].min *
(gdkdev->axes[i].max_value - axis_data[i])) /
win32/gdkinput-win32.c: (gdkdev->axes[i].max_value -
gdkdev->axes[i].min_value);
win32/gdkinput-win32.c- break;
But maybe they were not initialized for some reason. Would have to insert a
few print statements to find out (or maybe there are already, try enabling
some of the GDK_DEBUG flags... although I don't remember any more whether you
need a special debug build for that to work).
_______________________________________________________
Reply to this item at:
<http://gna.org/bugs/?18692>
_______________________________________________
Nachricht geschickt von/durch Gna!
http://gna.org/
_______________________________________________
Mypaint-bugs mailing list
[email protected]
https://mail.gna.org/listinfo/mypaint-bugs
