Comments on: Prevent desktop lock or screensaver with PowerShell

By: Dmitry Sotnikov

Dmitry Sotnikov — Tue, 08 Sep 2009 19:38:11 +0000

My guess is that it will just stop at the border.

However, you can just make it move to the side and back by doing something like:

[System.Windows.Forms.Cursor]::Position = New-Object System.Drawing.Point((($Pos.X) + 1) , $Pos.Y)
[System.Windows.Forms.Cursor]::Position = New-Object System.Drawing.Point($Pos.X , $Pos.Y)

By: Vics

Vics — Tue, 08 Sep 2009 18:46:16 +0000

What happen when your program move the mouse enough times that the screen end, do yo get bips or what ?

By: Dmitry Sotnikov

Dmitry Sotnikov — Tue, 28 Jul 2009 15:16:36 +0000

Claus,

This is way-way better than what I originally used!

Learning something new every day. Thanks a lot for the tip!

Dmitry

By: Claus Thude Nielsen

Claus Thude Nielsen — Mon, 27 Jul 2009 10:15:55 +0000

I did something similar in AutoIt as well, just moving the mouse one “pixel”.

So I thought I would try the same in PowerShell, here is what I ended up with, it will move the mouse one “Pixel” to the right, which is hardly noticeable.

$Pos = [System.Windows.Forms.Cursor]::Position
[System.Windows.Forms.Cursor]::Position = New-Object System.Drawing.Point((($Pos.X) + 1) , $Pos.Y)

By: Aaron

Aaron — Wed, 22 Jul 2009 17:35:47 +0000

I did the same thing with AutoIt … however I just had the mouse move 1 pixel.

By: asf

asf — Mon, 29 Jun 2009 22:09:31 +0000

talk about using the wrong tool for the job, why is powershell even involved, just some excuse not to use a WSH script (I know its tagged a hack and you are a powershell guy, but still) The proper way to do this would be to use the windows api (You can call the native api with autoit, so using a key pressing hack there is even worse)

And a “.”? why not toggle the start menu with ctrl+esc or something (print screen maybe if the scripting supports an escape code for that)?

By: Dmitry Sotnikov

Dmitry Sotnikov — Mon, 29 Jun 2009 13:36:35 +0000

Yep, good comments. I love Jaykul’s stuff but wanted something simple and self-contained so I ended up with the keys approach.

By: stangm

stangm — Mon, 29 Jun 2009 13:21:24 +0000

Using Jaykul’s WASP to send mouse clicks would help with the input buffer problem, and remove the need for launching notepad to accept the keys.

Actually I did this a while back with a simple autoit script that I compiled as an .exe. So when I need this functionality I just run that program, and kill it when I’m done.