Hi,
Attached is a patch for FGMacOSXEventInput.[ch]xx
Torsten, Could you commit it with the following comments:
-
Fixed: wrong event name for abs-hat0-y
Modified: let AxisElement to generate normalized input (-1.0 to 1.0).
This can be temporal and can
>
> There is no (known) limit for the number of supported buttons or axes with
> this implementation other than those of your operating system. On linux,
> buttons, keys and axes are numbered by a 16bit unsigned integer which
> limits your number of each to 65536.
Thank you !
Good, until I find
> Some time ago, I have been playing with input.cxx so that FG takes all the
> buttons of my Saitek x52pro ( more than 36, that is ).
> I had to patch plib so that this work.
>
> Since input method changed, my trick is obsolete, so I was wondering if the
> new method based on linux input will take
Some time ago, I have been playing with input.cxx so that FG takes all the
buttons of my Saitek x52pro ( more than 36, that is ).
I had to patch plib so that this work.
Since input method changed, my trick is obsolete, so I was wondering if the
new method based on linux input will take more tha
Hi,
On Aug 28, 2009, at 4:28 AM, Torsten Dreyer wrote:
> thanks for that - it looks like you spent a lot of time on it ;-) I will soon
> merge your updates into my code which has changed a little bit since the last
> cvs commit. I hope to get it done by the weekend.
> Do you think your FGMacOSXE
> I've implemented Mac specific portion of generic input devices, and am
> testing it. The Mac specific source (including some local modification on
> FGEventInput.* and Makefile.am files) ATM are available at:
> http://macflightgear.sourceforge.net/wp-content/uploads/eventinput/FGMacEve
>ntInput.
Hi,
I've implemented Mac specific portion of generic input devices, and am testing
it.
The Mac specific source (including some local modification on FGEventInput.*
and Makefile.am files) ATM are available at:
http://macflightgear.sourceforge.net/wp-content/uploads/eventinput/FGMacEventInput.tg
On 21 Aug 2009, at 10:55, Tatsuhiro Nishioka wrote:
> I took a look at the code, and I believe I can implement the Mac
> portion of the new input event model using HID Manager.
>
> I'll post the patch when I finish implementing it.
I was 'responsible' (more like 'guilty') for some of the current
> Hi,
>
> This indeed is a good idea.
> I took a look at the code, and I believe I can implement the Mac
> portion of the new input event model using HID Manager.
>
> I'll post the patch when I finish implementing it.
>
> -
> Tatsuhiro Nishioka
Great! Looking forward to receiving your patch.
T
Hi,
This indeed is a good idea.
I took a look at the code, and I believe I can implement the Mac
portion of the new input event model using HID Manager.
I'll post the patch when I finish implementing it.
-
Tatsuhiro Nishioka
On 2009/08/05, at 5:37, Torsten Dreyer wrote:
> I Just found o
I have just commited basic support for the linux event devices.
It is disabled by default and has to be enabled by calling
./configure --with-eventinput
(Don't forget autogen.sh before that)
If enabled, FlightGear needs dbus-1 and hal devel packages for the headers and
libs.
The system is not co
That's very clever! No complaints from my end if you want to pursue this.
I suspect this would open up FlightGear to a lot of new and interesting
input hardware, and I bet many cockpit builders would welcome generic HID
support.
Regards,
Curt.
On Tue, Aug 4, 2009 at 3:37 PM, Torsten Dreyer wro
I Just found out that my notebook's lid switch is an input device:
I: Bus=0019 Vendor= Product=0005 Version=
N: Name="Lid Switch"
P: Phys=PNP0C0D/button/input0
S: Sysfs=/devices/LNXSYSTM:00/device:00/PNP0C0D:00/input/input5
U: Uniq=
H: Handlers=event5
B: EV=21
B: SW=1
So - FlightGear now
On Tuesday 04 August 2009 19:54:23 Torsten Dreyer wrote:
> I am currently playing with the input subsystem. This was triggered because
> I have two devices that currently do not work with FlightGear, neither
> Linux nor Windows.
> My idea is to extend the FGInput class so it can use the devices pre
Hi Torsten,
Hi,
>
> I am currently playing with the input subsystem. This was triggered because I
> have two devices that currently do not work with FlightGear, neither Linux
> nor
> Windows.
>
> 1. A set of rudder pedals that does not get recognized as a joystick from
> joydev, because it r
15 matches
Mail list logo
