Hi Torsten,
On Sep 15, 2009, at 10:20 PM, Torsten Dreyer wrote:
>> I guess it is safer to use button-0, button-1, ... button-N for button
>> event names so the names stays the same on different OSs. maybe we need to
>> pull out some info using ioctl to find the first hid event code for a given
>>
> I guess it is safer to use button-0, button-1, ... button-N for button
> event names so the names stays the same on different OSs. maybe we need to
> pull out some info using ioctl to find the first hid event code for a given
> device (e.g. 228 for joystick).
I think your are right, simply number
Hi Brant,
Though your problem should be looked and fixed, it is different from
this one since the generic input device support is not implemented on
windows yet.
Plus, it does nothing on any platform unless you make a configuration
file for your device under $FG_ROOT/input/event//product>
Indeed. I have a X52 joystick and it's very confusing to configure in the
joystick .xml file. When I updated to CVS recently, the hats buttons don't
work properly in windows. This should be looked at and fixed.
On Mon, Sep 14, 2009 at 6:45 PM, Tatsuhiro Nishioka
wrote:
> Hi,
>
> I've been testing
Hi,
I've been testing X52 joystick with FGLinuxEventInput.cxx on liunx and found
that button event names for joysticks/gamepad are very suspicious, and we need
to consider some other means of naming button events.
The problem is that a joystick (, mouse or gamepad) button can have wrong event
5 matches
Mail list logo
