Activity for Alexandre Hardy
-
Alexandre Hardy committed [078425] on Git
Fix instance with shift
-
Update documents for controller instance
-
Add instance with shift
-
Fix blocker code
-
Handle multiple controllers better
-
Hi! I think it should be possible to compile for M1 and M2 chips, if I recall correctly the types are well specified in the xfsprogs code, so it should work fine. However, I tried to access an XFS volume on a more recent XFS based linux install, and found that the xfsprogs currently in use is not compatible with recent XFS filesystems. As noted above, it will take quite some work to get that working. I am no longer on a Mac OS X system, so I will not be attempting to support the newer XFS filesystems...
-
Cleanup joymap_blocker
-
Always write the PID file to make kill always work
-
Add a library to limit joystick access to only joymap devices
-
Make skipping axes optional
-
Fix removal of device due to incorrect vendor and product
-
Only report declared axes
-
Fix multiple devices with same vendor and product id
-
Don't register code device if there is no code
-
Add kill command line argument
-
Home
-
More documentation fixes
-
Fix handling of shift in flags, when it is on its own
-
Increase number of axes to accomodate second hat
-
Add a link to the UI project by Rens
-
Documentation fixes
-
Home
-
Fix auto calibrate
-
Fix man page
-
Hi James, This bug should be fixed in joymap-0.5.0. joymap-0.5.0 also adds a few other options; * Ability to specify a joystick by event device number instead of vendor and product. * Daemonize option, to run the program in the background. * Handles removal and insertion of devices at runtime (no need to have the devices plugged in before you start). * You can now provide a search path for configuration files in the JOYMAP_PATH environment variable so config files don't have to use absolute paths...
-
Hi! joymap-0.5.0 now supports use f the "id" keyword for mapping the joysticks. The Id corresponds to the event device associated with the device. For example, if event6 is listed as a handler for the device in /proc/bus/input/devices, then you can specify id=6 in the mapping file. If you specify the id, then you should not specify the vendor and product id. joymap-0.5.0 supports plugging in and out of devices, but if you use the id, then you may find a new event kernel device has been allocated...
-
Update document
-
Honour the event id
-
Tabs to spaces
-
Calibrate calues based on input reporting on axes values, if requested
-
Update documentation
-
Update makefile to cleanup correctly
-
Update manual pages
-
Make daemonizing optional
-
Move config away from loadmap to single handler
-
Handle locking of devices correctly
-
Replace tabs with spaces
-
Handle devices plugged in after launch, and display input events for programming
-
Fix compile errors due to small buffer
-
Fix shift button
-
Fix mouse wheel events
-
Add a mouse speed setting to control mouse responsiveness
-
Use strict timing to control mouse movement, same as in osxjoymap
-
Recompile documentation
-
Adjust mouse speed for new assumptions about axes
-
Add min, max, deadzone and also the trinary flag
-
Don't try grab a device multiple times
-
Move install_event_handlers back again. No idea why I moved it in the first place
-
Pull in osxjoymap changes
-
Recompile program.pdf
-
Fix mouse button presses
-
Update README
-
Reduce the number of axes on the Code joystick
-
Don't die if we can't grab the device
-
Make it possible to open the code device
-
Remove trailing whitespace
-
Fix error messages reported by Wall
-
Correct setup for joystick code device
-
Catch more errors
-
Add cmdline matching for config
-
Safeguard opens...
-
Change tabs to spaces
-
More configuration
-
First pass at adding configuration
-
Update makekeys.sh
-
Added sync events to each event sent.
-
Hi! The original joymap code was actually designed for my own use, and thus has some shortcomings when it comes to duplicate devices. The original design goals: 1. Consistently identify devices in a HOTAS setup (joystick, throttle and rudder pedals) even after reboots and hotplug events. 2. Allow programmability of targets. That is a very broad statement, and was never written down. But the point was to identify devices by their vendor and product id so that the software tolerates reboots and hotplug...
-
Hi! The original joymap code was actually designed for my own use, and thus has some shortcomings when it comes to duplicate devices. The original design goals: Consistently identify devices in a HOTAS setup (joystick, throttle and rudder pedals) even after reboots and hotplug events. Allow programmability of targets. That is a very broad statement, and was never written down. But the point was to identify devices by their vendor and product id so that the software tolerates reboots and hotplug events...
-
Hi! Thanks for the feedback! I'm afraid I have not had time to work on fuse-xfs to keep it up to date. I generally use /usr/local/bin/xfs-cli which is installed with the package to access my disk drives when I lose access with macFUSE / osxFUSE. You can execute that in a terminal like this /usr/local/bin/xfs-cli /dev/rdisk1 (depending on which disk you want to access). You probably still need sudo The commands are fairly straight forward, if you are familiar with the terminal interface, and you can...
-
Make sure we disconnect sockets that are disconnected
-
Fix handling of code axes and buttons
-
Add patches for dosbox and wine for joymap client
-
Update readme
-
Add a dosbox patch
-
Fix button/key releases for axis mapping
-
Create a custom joymap library to link in directly to other programs
-
Hi Dave, The "shift" button can be used to change behaviour based on whether that button is pressed or not. However, that only applies to buttons and not to axes. You can achieve that effect by writing a "script". Use the "code" directive (to specify the program to execute) as well as "script" directives (to tell joymap how it should present your joysticks to the program) and then you can implement the switch between buttons an axes in code. Perhaps something like: if (js1.b[2]) { a[0] = 128; } else...
-
Most working C preprocessor
-
First pass implementation of a c preprocessor that gives us more of the information we need
-
Checkpoint
-
Checkpoint
-
Remove old files
-
Cleanup spacing
-
First pass at formatting. Some work to get fxc to compile on linux.
-
Added macro argument expansion, and lots more...
-
Checkpoint
-
Working toward C output
-
Hi Acris, Can you explain what you mean by "but axis doesn't work". Do you mean:...
-
Some C implementation of closures, when return etc
-
First attempts at producing C
-
More macros, NULL pointers etc
-
Hi Joe, I'm afraid I cannot say why the axes are being mapped differently to what...
-
Hi James, You are correct. The shift functionality is not working. Not sure at which...
-
Hi James, You are correct. The shift functionality is not working. Not sure at which...
-
Thank you for the kind offer. No donation of any sort is necessary, as I developed...
-
Thanks James. I notice that with jstest none of the buttons were ever reported as...
-
Thanks Dan, Good catch! Kind regards Alexandre
-
Hi James, I changed the mouse code in joymap-0.4.1 to cater for other users, and...
-
Hi Colin, I tested on a VM, and you should not need quotes around trinary. Maybe...
-
Hi Colin, I am surprised. It sounds like your joysticks are giving absolute 0 when...
1 >