From fcafd086c8be5f2870ef10080a7396df12422ecb Mon Sep 17 00:00:00 2001 From: DParent10 <127067984+DParent10@users.noreply.github.com> Date: Thu, 17 Sep 2026 11:51:47 -0400 Subject: [PATCH] docs: wheel slots, Synapse tilt requirement, and NAGA_DEBUG in the user guide Documents the Wheel Tilt Left/Right and Wheel Click slots from #23, notes that tilt must be Scroll Left/Right in the mouse's on-board profile to be learnable (found on hardware), updates the Learn Hardware Trigger section now that mouse-button triggers work on every slot, and points at NAGA_DEBUG. Co-Authored-By: Claude Fable 5.1 --- USER-GUIDE.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/USER-GUIDE.md b/USER-GUIDE.md index e7f46e4..74f0637 100644 --- a/USER-GUIDE.md +++ b/USER-GUIDE.md @@ -75,9 +75,15 @@ If all you want from the DPI buttons is browser Back and Forward, assign **Mouse Razer's [button mapping instructions](https://mysupport.razer.com/app/answers/detail/a_id/6400/) mention keeping Synapse running. On the tested mouse the on-board assignments kept working over Bluetooth with Synapse closed, but check the behavior on your own mouse and firmware before relying on it. +## Scroll wheel tilt and wheel click + +The mapping window has a **Wheel** card with three slots: **Wheel Tilt Left**, **Wheel Tilt Right** and **Wheel Click**. They start unpaired because tilt and click report differently per mouse. Click **Configure** on a slot, then **Learn Hardware Trigger…**, then tilt or click the wheel once. Choose an action and save. Once paired, the native scroll or click is suppressed and only your action runs, one action per tilt. + +If tilting does nothing during learning, check the mouse's on-board profile in Razer Synapse: tilt must be assigned to **Scroll Left** and **Scroll Right**. Some profiles leave tilt on Scroll Up/Down, and then a tilt is indistinguishable from rolling the wheel, so it cannot be learned. NagaController cannot change that assignment itself. + ## Learn Hardware Trigger for other mice -**Learn Hardware Trigger…** is not limited to the DPI buttons. Any button card can learn a trigger from any mouse whose buttons send a distinct signal, which is how NagaController can support Razer mice other than the Naga. It works best when the button sends a keystroke; buttons that send only a mouse click can currently be learned for the DPI Up and DPI Down cards, but not for the twelve side button cards. Clear a learned trigger with the small ⓧ next to the **Trigger:** label. +**Learn Hardware Trigger…** is not limited to the DPI and wheel slots. Any button card can learn a trigger from any mouse whose buttons send a distinct signal, whether a keystroke or an extra mouse button, which is how NagaController can support Razer mice other than the Naga. Clear a learned trigger with the small ⓧ next to the **Trigger:** label. ## Updates and saved settings @@ -91,4 +97,6 @@ tccutil reset Accessibility com.example.NagaController && tccutil reset ListenEv A green permission label alone does not confirm that button interception is working: test a mapped button on selected text. +To see per-event diagnostics, launch with `NAGA_DEBUG` set (the README's troubleshooting section has the exact command). A normal launch only logs permission and error state. + The app does not set up login startup automatically.