Build from source code

[TimurGuryev]

Hi!
When I build from source code and run installer.exe my mouse stops working after reboot (debug build X64; uninstaller.exe fixes).
Also file wrapper/input.h probably misses "#include <string>"

I want to contribute. What is the right way to build and debug driver?

[TimurGuryev]

Or maybe it would be easier if you implement feature by yourself)

Rawaccel now uses mouse speed as input.
I want rawaccel to use mouse distance offset from some point as input (similar to joystick).

In GUI it will probably be:

1. Checkbox (feature enabled/disabled)
2. TextBox for one number ("time to travel" or how much mouse offset is divided by to get input speed)
3. TextBox for one number (minimal offset for mouse to move; otherwise it would be hard to use Windows)

I guess there will be some difficulties in implementing as your callbacks should be called not only on mouse movement but every x milliseconds too.

[JacobPalecki]

Hello,

Multiple things here:

"wrapper/input.h probably misses "#include "
Yes, I have addressed this in my branch "userinterface" which includes UI overhaul for RA 2.0

"I want to contribute. What is the right way to build and debug driver?"
You are coming in at an interesting time. Right now the big thing that needs doing is taking userinterface branch from my repo and start cleaning up the UI.
As far as building and debugging driver, you will need:

• Windows SDK and WDK for your version of Windows 10 or 11
• MSVC, spectre-mitigated, C++/CLI support for v143 x64/x86 build toolds
• Avalonia (for building latest UI): https://avaloniaui.net/gettingstarted#installation

You will then need to build the entire solution. Before running installer.exe and restarting, you need to make sure that testsigning is enabled, which may be as simple as running a bcdedit command or may require BIOS edits. (This is the step that I would guess you have missed.)

"I want rawaccel to use mouse distance offset from some point as input (similar to joystick)."
Your algorithm as stated does not make much sense to me. How does the user set the "center point"? What happens when the user picks the mouse up (which happens through natural motion all the time)? Why would it be hard to use windows without minimal offset - that would be a function of the curve, right?

[TimurGuryev]

Thank you! It works with testsigning.

I used those links:

• .NET Framework 4.7.2
• SDK + WDK + MSVC libs
• after opening solution "Tools > NuGet Package Manager > Package Manager Console" and restore missing NuGet packages
• enable testsigning
• use pipe to see stdout "rawaccel.exe > output.txt"

How does the user set the "center point"? What happens when the user picks the mouse up?

Center point is where mouse was when driver started (or when feature was enabled). Only way for user to change center point is to pick mouse up