Quick Quetion: GetCursorPos()

[Jajjo]

Hey there,

I'm experimenting with GetCursorPos instead of "static_cast"in g the LOWORD and HIWORD params. This is because I want to work with positions relative to teh screen.

Myt question is this: Does the POINT object get updated when the mouse is outside of the edge of my program? If not, how do I constantly update the cursor position regardless of whether it's inside the edges of my program?

Thanks guys/gals.
-Jajjo

[Jajjo]

Also,

I found this on MSDN

Remarks

The cursor position is always specified in screen coordinates and is not affected by the mapping mode of the window that contains the cursor.

Is that answering my question? I 'm sorta new to all this and can't decipher that jargon :(

Ta
Jajjo

[YarrOfDoom]

I believe that quote from MSDN tells you that the coordinates that are returned always are absolute coordinates (pixels counted from the top-left corner of your screen), and not relative to the position and size of the window which contains the cursor.

You have to call GetCursorPos every time you want the current position of the cursor, and it works when your cursor is outside of your program's window too.

Here's an extra hint to help you out with future questions: you can easily test these kind of questions yourself by trying it, and outputting the results. It can save you a lot of time because you don't have wait for a response from someone else.

[Jajjo]

Cool, thanks man :)

I'll strive to test stuff myself in the future.

[weaknessforcats]

It's been a very long time but are they still using WinProc? I seem to remember putting in a handler for the WM_MOUSEMOVE message. Every time the mouse moves that handler gets called.

[Studlyami]

@YarrOfDoom
I believe that the pixels are counted from the primary monitor. This means that if you are working on multiple monitors you could receive negative coordinates as the primary monitor is 0,0.

[YarrOfDoom]

You're probably right about that, I'll try it out as soon as I've connected my KVM-switch here.

edit: apparently my KVM switch doesn't work with a DVI-VGA converter, so I can't test.