Recent changes to Home

Discussion for Home page

Alexandre Hardy — Thu, 24 Jul 2025 19:51:55 -0000

I see that you can also try change this with X-windows:

$ xinput list-props 16
Device 'JOYMAP Mouse':
    Device Enabled (151):   1
    Coordinate Transformation Matrix (153): 1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
    Device Accel Profile (282): 0
    Device Accel Constant Deceleration (283):   1.000000
    Device Accel Adaptive Deceleration (284):   1.000000
    Device Accel Velocity Scaling (285):    10.000000
    Device Product ID (271):    255, 2
    Device Node (272):  "/dev/input/event19"
    Evdev Axis Inversion (286): 0, 0
    Evdev Axes Swap (288):  0
    Axis Labels (289):  "Rel X" (161), "Rel Y" (162), "Rel Vert Wheel" (281)
    Button Labels (290):    "Button Left" (154), "Button Middle" (155), "Button Right" (156), "Button Wheel Up" (157), "Button Wheel Down" (158), "Button Horiz Wheel Left" (159), "Button Horiz Wheel Right" (160)
    Evdev Scrolling Distance (291): 1, 1, 1
    Evdev Middle Button Emulation (292):    0
    Evdev Middle Button Timeout (293):  50
    Evdev Middle Button Button (294):   2
    Evdev Third Button Emulation (295): 0
    Evdev Third Button Emulation Timeout (296): 1000
    Evdev Third Button Emulation Button (297):  3
    Evdev Third Button Emulation Threshold (298):   20
    Evdev Wheel Emulation (299):    0
    Evdev Wheel Emulation Axes (300):   0, 0, 4, 5
    Evdev Wheel Emulation Inertia (301):    10
    Evdev Wheel Emulation Timeout (302):    200
    Evdev Wheel Emulation Button (303): 4
    Evdev Drag Lock Buttons (304):  0

$ xinput set-prop 16 'Evdev Scrolling Distance' 10, 10, 10

In this case I changed the device so that ten input events cause 1 unit of scroll, instead of 1. It seems to help to make things smoother.

You would have to investigate what the device number is, on my system it is 16 for the Joymap virtual mouse.

Kind regards
Alexandre

Discussion for Home page

Alexandre Hardy — Thu, 24 Jul 2025 19:40:47 -0000

Hi Michael,

I checked the code again, speed=1 is the slowest reporting rate possible. However, we can make it slower by adding delays between reporting events.

I tested with the following:

# Get input from the script
button vendor=0x00ff product=0x0000 src=0 target=mouse axis=8 speed=1
button vendor=0x00ff product=0x0000 src=1 target=mouse axis=8 flags=invert speed=1
button vendor=0x00ff product=0x0000 src=0 target=mouse axis=8 flags=release speed=1
button vendor=0x00ff product=0x0000 src=1 target=mouse axis=8 flags=invert,release speed=1

#assign a joystick number for script purposes
script vendor=0x044f product=0x0402 device=0 #Thrustmaster Warthog Joystick
script vendor=0x044f product=0x0404 device=1 #Thrustmaster Warthog Throttle
script vendor=0x068e product=0x00f2 device=2 #CH Pedals

code "mouse.code"

Note the vendor is 0x00ff which is actually a virtual joystick that joymap creates. The output for the virtual joystick is set in "mouse.code":

global scroll_up;
global scroll_down;

if (firstscan) {
    scroll_up = 0;
    scroll_down = 0;
}

if (js0.b[6]) {
    scroll_up = 1;
}
if (js0.b[8]) {
    scroll_down = 1;
}

if (scroll_up) {
    thread up {
        b[0] = 1;
        delay(10);
        b[0] = 0;
        delay(20);
        scroll_up = 0;
    }
}

if (scroll_down) {
    thread down {
        b[1] = 1;
        delay(10);
        b[1] = 0;
        delay(20);
        scroll_down = 0;
    }
}

It looks a bit complicated, but it gets easier when you get used to it. The idea is that a button press starts a "thread". The thread executes until the thread itself sets a variable to say the thread is done. (This is necessary because of how threads are implemented in joymap, a thread is actually just a separate instruction pointer that is incremented at each iteration of the script, assuming the thread is executed).

In the thread we turn the button on for a short while, and then off for a short while. The delay ensures that we don't report the button as on all the time even if you hold it in on the joystick. You can play with the value (20) and make it longer for longer delays. You can also play with the value (10) to reduce the period of time over which the scroll event is reported.

I haven't managed to get it to scroll more smoothly. I see there is hi-res scrolling support in the kernel, and this should enable it:

ff --git a/devices.c b/devices.c
index 4e59e8c..fd016e1 100644
--- a/devices.c
+++ b/devices.c
@@ -282,7 +282,7 @@ void register_devices(int add_code_device) {
     safe_ioctl3(mouse_fd, UI_SET_KEYBIT, BTN_RIGHT);
     safe_ioctl3(mouse_fd, UI_SET_RELBIT, REL_X);
     safe_ioctl3(mouse_fd, UI_SET_RELBIT, REL_Y);
-    safe_ioctl3(mouse_fd, UI_SET_RELBIT, REL_WHEEL);
+    safe_ioctl3(mouse_fd, UI_SET_RELBIT, REL_WHEEL_HI_RES);

     sprintf(dev.name, "JOYMAP Mouse");
     dev.id.bustype = BUS_VIRTUAL;
@@ -429,7 +429,7 @@ void send_move_mouse_wheel(int dwheel) {
     struct input_event event;
     gettimeofday(&event.time, NULL);
     event.type=EV_REL;
-    event.code=REL_WHEEL;
+    event.code=REL_WHEEL_HI_RES;
     event.value=dwheel;
     safe_write(mouse_fd, &event, sizeof(event));
     event.type=EV_SYN;

... but it does not work for me, so I cannot confirm that it s a good change to make.

Discussion for Home page

Michael Stanczyk — Mon, 14 Jul 2025 21:30:58 -0000

Using a ch products pro throttle:
button vendor=0x068e product=0x00f1 src=0 target=mouse axis=8 flags=invert speed=1
button vendor=0x068e product=0x00f1 src=0 target=mouse axis=8 flags=invert,release speed=1

button vendor=0x068e product=0x00f1 src=2 target=mouse axis=8 speed=1
button vendor=0x068e product=0x00f1 src=2 target=mouse axis=8 flags=release speed=1

these lines work for direction but the speed is still too fast when I click the hat. when i spin my mouse wheel slowly it clicks and generates a mouse scroll event. can I get that behavior here?

Alternatively can you explain how to script a action to a button press? If I make a variable current_button that outputs a keyboard press of the current_button the increments the value thatcould work. So if current_button is three, it sends a keyboard press of the 3 key/

Discussion for Home page

Alexandre Hardy — Sun, 13 Jul 2025 19:19:35 -0000

Hi Michael,

Sorry for the late reply. The wheel is programmed as follows:

button vendor=0x044f product=0x0402 src=6 target=mouse axis=8
button vendor=0x044f product=0x0402 src=8 target=mouse axis=8 flags=invert
button vendor=0x044f product=0x0402 src=6 target=mouse axis=8 flags=release
button vendor=0x044f product=0x0402 src=8 target=mouse axis=8 flags=invert,release

#assign a joystick number for script purposes
script vendor=0x044f product=0x0402 device=0 #Thrustmaster Warthog Joystick
script vendor=0x044f product=0x0404 device=1 #Thrustmaster Warthog Throttle
script vendor=0x068e product=0x00f2 device=2 #CH Pedals

Note that there are four entries:
* Button press to scroll up
* Button release for scroll up
* Button press for scroll down
* Button release for scroll down

This example allows me to use one of the multiway switches on the Thrustmaster Warthog joystick to scroll up and down.

The magic number "8" for the axis comes from /usr/include/linux/input-event-codes.h (on my system it is here) under the constant ABS_WHEEL. You can use ABS_X (0) or ABS_Y (1) or ABS_WHEEL (8).

Please also check doc/config.pdf for details about the "speed" setting to control the speed of scrolling. You may need to adjust things if your scrolling has to be precise.

Hope that helps!

Kind regards
Alexandre

Discussion for Home page

Michael Stanczyk — Thu, 19 Jun 2025 00:51:07 -0000

How do I map a button to the mouse scroll wheel? I have some games that only allow you select different hotbar slots via the mouse scroll wheel. Minecraft only allows you change from hotbar slot 1 to slot 2 by either the scroll wheel or by pressing 2. Half-life 2 only allows weapon selection via the scroll wheel.

Oh do you have a donation link somewhere? Having this continue to exist is really important to me for my current and future gaming needs.

Discussion for Home page

Alexandre Hardy — Sat, 24 May 2025 20:26:09 -0000

Thanks for catching that!

New version pushed and uploaded.

Feel free to push more patches my way, especially when I mess up. :-)

Kind regards
Alexandre

Discussion for Home page

patlefort — Sat, 24 May 2025 16:57:49 -0000

Your code works fine except you forgot to add the new config keys in known_keys in mapparser.c. Thank you very much.

Discussion for Home page

Alexandre Hardy — Sat, 24 May 2025 12:16:05 -0000

I've had a look at the patch, thanks again for that.

I'm going to make a few changes though. The original code allowed device values to be passed through unaltered. In other words, if min and max weren't specified, then we would get the value from the device directly. If min and max are specified, then the output would be rescaled based on that range. I've changed the config a bit (backward compatible though) and the documentation to make that clearer.

The patched you supplied changes that behaviour, so that scaling is always applied. However, the original min and max value was designed to tell you about the input behaviour. And the main adjustment in the patch as I see it is to change the output behaviour.

So I'm going to adjust the patch a little bit so that the input behaviour remains the same as it was (but the rescaling code is fine, no objections to that) and that the output settings are carried across as specified.

It is a great patch though, I've never tried to use the hat switch for some reason (for some reason I've always resorted to using the keyboard commands for views in flightsims instead of the switching hat because I like the snap to 3 o'clock, 6 o'clock and 9 o'clock positions).

Please check the pushed code, or joymap version 0.6.0 to see if it still solves your problem.

And thanks again for the patch! It made my life a lot easier...

Kind regards
Alexandre

Discussion for Home page

Alexandre Hardy — Sat, 24 May 2025 11:22:29 -0000

Hi!

Thank you for the feedback! Sorry for the late reply, I've been somewhat busy.

Thank you for the patch! It is great to see a contribution in this form, I'll look at it shortly.

Kind regards
Alexandre

Discussion for Home page

patlefort — Sun, 04 May 2025 23:43:27 -0000

Here's a patch that fixes a few issues:
* Set min and max axis values to the virtual device from map config. This enable SDL to detect axis as "hats" when the range is -1 to 1.
* Set the default minimum to -32768 instead, which fix the issue I was having above.
* Fix formula to rescale axis value between -32767 and 32767.
* Round and clamp value when rescaling value when we have a deadzone.
* Change dev.absfuzz[i] to dev.absfuzz[j] in register_devices.