I’ve been looking to implement Windows OS specific code for the mouse… Like mouse warp, hiding the mouse etc.
However I’m having some trouble figuring out what the idea behind the architecture is.
A lot of the mouse functions (like MoveCursor and ShowCursor) have an SDL_Cursor as parameter.
I wouldn’t know what to do with those parameters, as, (the way I see it) windows always has one mouse pointer with one cursor
and the current cursor is either visible or it isn’t…
Same goes for WarpMouse, which takes parameters Mouse and Window… While in windows, I perceive it to be just one mouse, and
Then there’s the function MoveCursor, which has comment above it stating: "Is Called when a mouse motion event occurs"
However If I look at a standard windows implementation, the mouse cursor will already have moved on a motion event… it’s the mouse
that generates these events in the first place.
The only way I can think of this making sense, is if the idea is to read the devices directly or something, and do all the actual mouse operations of placing the cursor and such, in software.
So if these functions were made to be a software implementation of device driven mouse movement, why are the cursor functions OS specific? And wouldn’t that need some kind of polling mechanism? As windows usually only tells the program about the mouse through windows messages?
In short, I’m kinda lost here on what’s to be build, and have no idea how this is meant to be implemented.
If someone could give me a few pointers on what to do to get the mouse grabbing/hiding etc to work, that would be great…
Or perhaps someone else is already working on this?