Would like to restrict axis movement without affecting button operation

[klmonline]

XMBC Version: 2.20.5
Installed or Portable version: Installed
Windows Version: Win 11 Home x64
Mouse Information (brand/model): Delux M618PLUS
Relevant Computer Information (CPU, RAM etc): Ryzen 7 3700X, 32GB RAM
Did the problem occur after an upgrade of XMBC? (If so, from what version?): NO
Did the problem occur after a Windows update/upgrade? (If so, from what version?): NO
How long have you used XMBC?: 5 years
What language and keyboard layout do you use in Windows?: American English QWERTY

I have an application-specific buttons profile for GoldWave audio editing software (v 7.01). GoldWave default behavior lets me hold and drag the middle mouse button to move the displayed audio waveform within the main app display window. I would like to restrict the movement to X-axis only (so lock the Y-axis), but I cannot set this option while the Middle Button is on "No Change (Don't intercept)" in XMBC. So far, any other setting I attempt to give the Middle Button disables the hold and drag functionality within GoldWave. For instance, I tried changing the XMBC middle button setting to Lock Y-Axis While Pressed, and it changed the mouse behavior to stay on the X-axis, but the app no longer drags the visual area. Is there a way to restrict axis movement of the mouse without affecting whatever held middle button status the app is checking?

[phil]

You could try...
Middle button -> Simulated Keystrokes
In the main input, enter: {LOCKY}
Set Method to 3 (During)
Un-tick the box: Block original message

Untitled.png

Give the a go, let me know if it works or not!

EDIT: Fixed the typo mentioned below!

[klmonline]

You are the best! Worked like a charm.

In case any other unsophisticated types are reading this later, note that a small typo crept into the keystroke suggestion. It should be {LOCKY} rather than {LOCYY}

Thanks so much for the great software and the fast, helpful response on the forum.

[phil]

Great, glad that worked. I fixed the typo above (thanks for pointing that out )