setcursorpos() not working on y axis.

[medic5678]

this should be pretty simple.

Declare PtrSafe Function SetCursorPos Lib "user32" (ByVal x As Long, ByVal y As Long) As Long

I was capturing the mouse position with GetCursorPos, and I noticed that it would always treat the y value as zero.

So I put in manual coordinates, and it still does the same thing.

Sub Setcursor()


SetCursorPos 300, 100


End Sub

whatever I change the x value to (first value) works fine going across the screen horizontally. Vertically, any number I put in is treated as 0.

I'm using this in a userform.

 

[Yongle]

Try replacing

Declare PtrSafe Function SetCursorPos Lib "user32" (ByVal x As Long, ByVal y As Long) As Long

with

Declare PtrSafe Function SetCursorPos Lib "user32" (ByVal x As Long[COLOR=#ff0000]Ptr[/COLOR], ByVal y As Long[COLOR=#ff0000]Ptr[/COLOR]) As Long[COLOR=#ff0000]Ptr[/COLOR]

 

[RoryA]

The declaration is correct as it was and should not be changed. It also works fine for me as written - what version of Office and Windows are you using?

 

[medic5678]

Excel 2016, 64 bit windows 10

 

[RoryA]

I don't have that available to me here, but can try it later. Is it 64bit Office as well? (not that it affects the code)

 

[medic5678]

I think I'll create a blank form in a new project and try this to determine if it's something with the environment or some curious interaction with my project.

 

[Yongle]

It works with Windows 10 and Excel 2016 (32 bit) for me

 

[medic5678]

I don't have that available to me here, but can try it later. Is it 64bit Office as well? (not that it affects the code)

yes. Office 2016 64 bit. Thanks for the replies, this tells me I need to experiment a bit more.

 

[Yongle]

The fact that one co-ordinate worked and not the other suggests that the original code is probably ok and that someting else is causing the problem
- I do not understand the mechanics behind the scenes but slavishly follow what Microsoft says
- RoryA is very knowlegeable and is probably correct but did you try my suggestion?

https://docs.microsoft.com/en-us/office/vba/language/reference/user-interface-help/longptr-data-type
this is what Microsoft says:
LongPtr is not a true data type because it transforms to a Long in 32-bit environments, or a LongLong in 64-bit environments.
Using LongPtr enables writing portable code that can run in both 32-bit and 64-bit environments. Use LongPtr for pointers and handles

 

[medic5678]

The fact that one co-ordinate worked and not the other suggests that the original code is probably ok and that someting else is causing the problem
- I do not understand the mechanics behind the scenes but slavishly follow what Microsoft says
- RoryA is very knowlegeable and is probably correct but did you try my suggestion?

https://docs.microsoft.com/en-us/office/vba/language/reference/user-interface-help/longptr-data-type
this is what Microsoft says:
LongPtr is not a true data type because it transforms to a Long in 32-bit environments, or a LongLong in 64-bit environments.
Using LongPtr enables writing portable code that can run in both 32-bit and 64-bit environments. Use LongPtr for pointers and handles

Trying it now. Thanks for the suggestion. By the lunch I'll know a lot more . The wife's got me doing chores, so my time is limited until the evening.