Mousemove doesn't move cursor

[Alodar]

In windows 7 on a single machine, the mousemove command does not work. It moves the mouse sort of (by which I mean a tooltip for where I've supposedly moved the mouse appears), but the cursor itself, and thus any 'click' events do not get moved. Any ideas on how I can figure out why this is happening on this machine? It's all up to date via service packs and the like, UAC is off, RequireAdmin is on...

What can I do to troubleshoot/fix this?

[chachew]

I have tested this exact scenario with Win7 x64 and MouseMove works perfectly....what is the code you are running?

[Alodar]

Well, I'm running 32, not 64, but shouldn't really make a difference?

Run("C:\Program Files\LogMeIn\x86\LogMeInToolkit.exe")
WinWait("LogMeIn")
WinActivate("LogMeIn")
Opt("MouseCoordMode", 0)
MouseMove(30, 65)
Sleep(5000)
MouseClick("left", 30, 65)
Sleep(30000)
MouseClick("left", 30, 65)

I don't even get to the MouseClick point because the MouseMove event doesn't have anything happen.

Edited October 24, 2011 by Alodar

[JohnOne]

Did it occur to you that

WinWait("LogMeIn")

may not be completing?

Try just MouseMove(0,0) on its own.

[chachew]

Did it occur to you that

WinWait("LogMeIn")

may not be completing?

Try just MouseMove(0,0) on its own.

Shouldnt matter the version of the OS

I ran this script and it all works for me, i suggest that you look into the WinWait..as JohnOne said

Edited October 24, 2011 by chachew

[Alodar]

Yeah, I did check that. I removed everything except MouseMove itself. I commented out the Opt Coordmode also to see if that would make a difference, but it didn't seem to make a difference either. It works fine everywhere except on this one computer, so I'm betting it's something weird with the install or something, but I have no idea how or where to check it.

[JohnOne]

Sounds as though there is something seriously wrong with the OS installation, or some sort of gung ho security layer in a firewall or something intercepting some Windows API.

I'm just rambling though.

Just for reference, what is the spec of the computer? is it some virtual machine installed, is it mac with wine etc...

This info is no good to me, but might be for someone else, I'd just wipe it and re-install windows (drastic)

You could proceed by checking other Autoit native functions, and maybe some _WinAPI* functions to move the mouse and log the results of those.

[JohnOne]

Try this, should move the mouse 200 right and 200 down

#Include <WinAPI.au3>
#include <Constants.au3>
_WinAPI_Mouse_Event($MOUSEEVENTF_MOVE , 200 , 200 )

[Alodar]

Nope, didn't do anything. The install is a Windows 7 install on a dell (it's the 'Dell install' type of thing). So I can't really install base windows 7, cause of Dell's retardation for drivers and the like. Plus, it's a work computer, so it would be frowned on.

It's just this one computer doing it, it's really odd. I'm starting to think I'll just have to find a way to do it with keyboard commands (tab around until I get to stuff and use spacebar and the like).

[francoiste]

i'm experiencing the same issue (with AutoIt v3.3.12.0 plus SciTE4AutoIt3 14.801.2025.0):

• Win7 SP1 (x64), running on physical machine - MouseMove working OK
• Win7 SP1 (x64), running as guest in vmware workstation 9.0.4 - MouseMove does NOT work

in the VM i have installed vmware tools: "vmtoolsd.exe" with file version 9.2.4.27715

example code:

Sleep(1000)
Local $aPos1 = MouseGetPos()

MouseMove(5, 5, 0)

Sleep(1000)
Local $aPos2 = MouseGetPos()

If ($aPos2[0] <> 5) Or ($aPos2[0] <> 5) Then
    MsgBox(0, "ERROR", "MouseMove failed:" & @CRLF _
    & "old pos: " & $aPos1[0] & "," & $aPos1[1] & @CRLF _
    & "new pos: " & $aPos2[0] & "," & $aPos2[1] )
Else
    MsgBox(0, "SUCCESS", "MouseMove succeeded.")
EndIf

strangely it thinks it was successful.

however, the mouse cursor is not moved!

Edited June 9, 2015 by francoiste

[BrewManNH]

Sounds like a VMWare issue, as it's working on a physical machine.

[MattM]

I fixed this by using the "Compile script to .exe" tool and running the generated executable as Administrator. Works in Windows 7 and Windows 10.

[JLogan3o13]

@MattM Did you notice this thread is almost 4 years old? Please don't resurrect old posts; the language has changed a lot in 4 years, what worked then may not today.