Ansible
PS DSC
Downloads:
14
Downloads of v 1.0.0:
14
Last Update:
03 Jun 2023
Package Maintainer(s):
Software Author(s):
- foundata
Tags:
chocolatey-sendmouseclick.extension mouse-events mouse-emulation click non-silent user32.dll- Software Specific:
- Software Site
- Software Source
- Software License
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Chocolatey Send-MouseClick extension
- Software Specific:
- Software Site
- Software Source
- Software License
- Software Docs
- Software Issues
- Package Specific:
- Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
14
Downloads of v 1.0.0:
14
Maintainer(s):
Software Author(s):
- foundata
Chocolatey Send-MouseClick extension
Legal Disclaimer: Neither this package nor Chocolatey Software, Inc. are affiliated with or endorsed by foundata. The inclusion of foundata trademark(s), if any, upon this webpage is solely to identify foundata goods or services and not for commercial purposes.
- 1
- 2
- 3
All Checks are Passing
3 Passing Tests
WARNING
This package was rejected on 19 Aug 2023. The reviewer TheCakeIsNaOH has listed the following reason(s):
Description
A Chocolatey extension providing helper functions to send mouse clicks (mouse related SendInput calls). These functions may be used in Chocolatey install and uninstall scripts by declaring this package a dependency in your package's .nuspec.
Files
extensions\chocolatey-sendmouseclick.extension.psm1
$ErrorActionPreference = 'Stop' # stop on all errors
$scriptRoot = Split-Path $MyInvocation.MyCommand.Definition
# get currently defined functions (before dot sourcing additional .ps1 files)
$functionsBefore = Get-ChildItem 'Function:\*'
# dot source files whose names start with a capital letter, ignore others
Get-ChildItem "${scriptRoot}\*.ps1" | Where-Object { $PSItem.Name -cmatch '^[A-Z]+' } | ForEach-Object { . $PSItem }
# get currently defined functions (after dot sourcing additional .ps1 files)
$functionsAfter = Get-ChildItem 'Function:\*'
# export functions whose names start with a capital letter, others are private
$functionsDiff = Compare-Object $functionsBefore $functionsAfter | Select-Object -ExpandProperty 'InputObject' | Select-Object -ExpandProperty 'Name'
$functionsDiff | Where-Object { $PSItem -cmatch '^[A-Z]+'} | ForEach-Object { Export-ModuleMember -Function $PSItem }
extensions\Helper.ps1
Add-Type -Language 'CSharp' -ReferencedAssemblies @('System', 'System.Drawing', 'System.Runtime.InteropServices', 'System.Windows.Forms') -TypeDefinition @"
using System;
using System.Drawing;
using System.Runtime.InteropServices;
using System.Windows.Forms;
public static class MouseClick
{
// More info on INPUT structure (winuser.h):
// https://learn.microsoft.com/en-us/windows/win32/api/winuser/ns-winuser-input
[StructLayout(LayoutKind.Sequential)]
public struct INPUT
{
public int type; // 0 = INPUT_MOUSE, 1 = INPUT_KEYBOARD, 2 = INPUT_HARDWARE
public MOUSEINPUT mInput;
}
// More info on MOUSEINPUT structure (winuser.h):
// https://learn.microsoft.com/en-us/windows/win32/api/winuser/ns-winuser-mouseinput
[StructLayout(LayoutKind.Sequential)]
public struct MOUSEINPUT
{
public int dx;
public int dy;
public int mouseData;
public int dwFlags;
public int time;
public IntPtr dwExtraInfo;
}
// See https://learn.microsoft.com/en-us/windows/win32/api/winuser/ns-winuser-mouseinput
// for info about the following bit flags that specify various aspects of mouse motion,
// button clicks and other mouse events or functions.
private const int MOUSEEVENTF_ABSOLUTE = 0x8000;
private const int MOUSEEVENTF_HWHEEL = 0x1000;
private const int MOUSEEVENTF_LEFTDOWN = 0x0002;
private const int MOUSEEVENTF_LEFTUP = 0x0004;
private const int MOUSEEVENTF_MIDDLEDOWN = 0x0020;
private const int MOUSEEVENTF_MIDDLEUP = 0x0040;
private const int MOUSEEVENTF_MOVE = 0x0001;
private const int MOUSEEVENTF_RIGHTDOWN = 0x0008;
private const int MOUSEEVENTF_RIGHTUP = 0x0010;
private const int MOUSEEVENTF_WHEEL = 0x0080;
private const int MOUSEEVENTF_XDOWN = 0x0100;
private const int MOUSEEVENTF_XUP = 0x0200;
[DllImport("user32.dll")]
extern static uint SendInput(uint nInputs, INPUT[] pInputs, int cbSize);
public static void LeftClickAtPoint(int x, int y)
{
// move
INPUT[] input = new INPUT[3];
input[0].mInput.dx = x * (65535 / System.Windows.Forms.Screen.PrimaryScreen.Bounds.Width);
input[0].mInput.dy = y * (65535 / System.Windows.Forms.Screen.PrimaryScreen.Bounds.Height);
input[0].mInput.dwFlags = MOUSEEVENTF_MOVE | MOUSEEVENTF_ABSOLUTE;
// left button down
input[1].mInput.dwFlags = MOUSEEVENTF_LEFTDOWN;
// left button up
input[2].mInput.dwFlags = MOUSEEVENTF_LEFTUP;
SendInput(3, input, Marshal.SizeOf(input[0]));
}
}
"@
extensions\Send-MouseClick.ps1
function Send-MouseClick {
<#
.SYNOPSIS
Sends mouse clicks to the active application with optional, automatic window
focus and optional delays (before and after clicking). Mostly a wrapper
around different mouse click related user32.dll SendInput calls.
.LINK
https://docs.microsoft.com/en-us/dotnet/desktop/winforms/input-mouse/how-to-simulate-events
#>
[CmdletBinding()]
Param(
[Parameter(Mandatory = $False,
HelpMessage = 'Where to send the click (this does not move the cursor, only sending the click as it would have been moved there and back to the original position). Use $False, $null or an empty string to send the click at the current cursor position. Use the string "Center" to send the click to the center of the current primary screen. User an array of integers (x, y) to define coordinates as you whish. Defaults to "Center".')]
$Position = 'Center',
[Parameter(Mandatory = $False,
HelpMessage = 'What kind of mouse click to send. Defaults to "Left".')]
[ValidateSet('Left')]
[String]$Type = 'Left',
[Parameter(Mandatory = $False,
HelpMessage = 'Array of integers. Seconds to wait before executing the mouse event and afterwards. Defaults to (0, 2).')]
[ValidateScript({
if (!($Delay -is [array]) -or ($Delay.count -ne 2)) {
Throw 'Send-MouseClick: -Delay has to be an array of integers with two elements.'
} else {
$True
}
})]
[Array]$Delay = @(0, 2),
[Parameter(Mandatory = $False,
HelpMessage = 'An optional -Query for Use-Window (which will be called before the mouse click if a query is given).')]
[String]$Query = ''
)
Begin {
if (!(Test-Path variable:SendMouseClickInitDone -ErrorAction 'SilentlyContinue')) {
Add-Type -AssemblyName System.Drawing
Add-Type -AssemblyName System.Windows.Forms
Set-Variable -Name 'SendMouseClickInitDone' -Value $True -Option 'Constant' -Scope 'Global' -Force
}
}
Process {
$Coordinates = @(0, 0)
switch ($Position) {
# center of primary screen
'Center' {
# TODO Check if this is DPI aware, not tested yet. Cf. bit.ly/3E7L4Z3, bit.ly/3hsEySV
# TODO Check if PrimaryScreen.WorkingArea is better (which returns the desktop area
# of the display, excluding taskbars, docked windows, and docked tool bars)?
# Clarify where do new windows get placed? Center of screen or working area?
# Cf. System.Windows.WindowStartupLocation.CenterScreen
$Coordinates[0] = [int]([System.Windows.Forms.Screen]::PrimaryScreen.Bounds.Width / 2)
$Coordinates[1] = [int]([System.Windows.Forms.Screen]::PrimaryScreen.Bounds.Height / 2)
}
# user defined position
{(($Position -is [array]) -and ($Position.count -eq 2))} {
$Coordinates[0] = [int]$Position[0]
$Coordinates[1] = [int]$Position[1]
}
# cursor's current position
{($Position -eq $False -or ([string]::IsNullOrEmpty($Position)))} {
$Coordinates[0] = [int]([System.Windows.Forms.Cursor]::Position.X)
$Coordinates[1] = [int]([System.Windows.Forms.Cursor]::Position.Y)
}
default { Throw ('Send-MouseClick: Unknown position "{0}"' -f "${Position}") }
}
# force integer casting
$Delay[0] = [int]$Delay[0]
$Delay[1] = [int]$Delay[1]
# delay before
if ($Delay[0] -gt 0) {
Write-Host ('Send-MouseClick: Will wait {0} seconds (delay before sending the click(s)).' -f $Delay[0])
Start-Sleep $Delay[0]
}
# bring to front and activate a target window
if ($Query -ne $False -and !([string]::IsNullOrEmpty($Query))) {
Use-Window -Query $Query
}
Write-Host ('Send-MouseClick: "{0}" click at (X{1}, Y{2}).' -f "${Type}", $Coordinates[0], $Coordinates[1])
switch ($Type) {
'Left' { [MouseClick]::LeftClickAtPoint($Coordinates[0], $Coordinates[1]) }
# 'LeftDouble' { FIXME to be implemented }
# 'Right' { FIXME to be implemented }
default { Throw ('Send-MouseClick: Unknown click type "{0}"' -f "${Type}") }
}
# delay after
if ($Delay[1] -gt 0) {
Write-Host ('Send-MouseClick: Will wait {0} seconds (delay after sending the click(s)).' -f $Delay[1])
Start-Sleep $Delay[1]
}
}
End { }
}
Virus Scan Results
Log in or click on link to see number of positives.
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
Copyright
Copyright (c) 2023 foundata GmbH (https://github.com/foundata/chocolatey-sendmouseclick.extension)
Dependencies
-
- chocolatey-usewindow.extension (≥ 0.0.1)
Discussion for the Chocolatey Send-MouseClick extension Package
Ground Rules:
- This discussion is only about Chocolatey Send-MouseClick extension and the Chocolatey Send-MouseClick extension package. If you have feedback for Chocolatey, please contact the Google Group.
- This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
- The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
- Tell us what you love about the package or Chocolatey Send-MouseClick extension, or tell us what needs improvement.
- Share your experiences with the package, or extra configuration or gotchas that you've found.
- If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.
foundata (maintainer) on 03 Jun 2023 21:07:13 +00:00:
User 'foundata' (maintainer) submitted package.
chocolatey-ops (reviewer) on 03 Jun 2023 21:41:07 +00:00:
chocolatey-sendmouseclick.extension has passed automated validation. It may have or may still fail other checks like testing (verification).
NOTE: No required changes that the validator checks have been flagged! It is appreciated if you fix other items, but only Requirements will hold up a package version from approval. A human review could still turn up issues a computer may not easily find.
Guidelines
Guidelines are strong suggestions that improve the quality of a package version. These are considered something to fix for next time to increase the quality of the package. Over time Guidelines can become Requirements. A package version can be approved without addressing Guideline comments but will reduce the quality of the package.
Notes
Notes typically flag things for both you and the reviewer to go over. Sometimes this is the use of things that may or may not be necessary given the constraints of what you are trying to do and/or are harder for automation to flag for other reasons. Items found in Notes might be Requirements depending on the context. A package version can be approved without addressing Note comments.
foundata (maintainer) on 03 Jun 2023 21:55:38 +00:00:
If the review team is wondering what this is all about: We need to automate non-silent installers of old or niche software quite often. Depending on additional software like AutoHotKey (AHK) is not an option for us in these environments.
We therefore developed two lightweight extensions which are only using out-of-the-box PowerShell/.NET and thought this is might be useful for others, too. So we are able to interact with non-silent setup wizards easily by focusing their windows and sending keystrokes or mouse clicks:
We understand a bit more of example code and documentation has to be added to make these extensions more useful for the community and someone who is searching for AHK alternatives. We already created issues for this and will provide better documentation soon:
Cheers,
Andreas
foundata (maintainer) on 03 Jun 2023 22:00:35 +00:00:
ProjectUrlandProjectSourceUrlare the same. It makes sense to send users to the repository, showing the renderedREADME.mdat this point in time, no matter if a user wants to know more about the package in general or to look at the source code.releaseNoteswill be filled out (pointing toCHANGELOG.md) on the first update.chocolatey-ops (reviewer) on 03 Jun 2023 22:00:40 +00:00:
chocolatey-sendmouseclick.extension has passed automated package testing (verification). The next step in the process is package scanning.
Please visit https://gist.github.com/choco-bot/1578187959e1c83ab51db10983f45f25 for details.
This is an FYI only. There is no action you need to take.
chocolatey-ops (reviewer) on 03 Jun 2023 22:15:24 +00:00:
chocolatey-sendmouseclick.extension has passed automated virus scanning.
flcdrg (reviewer) on 26 Jul 2023 11:02:20 +00:00:
Hi there,
unfortunately you will need to resubmit this package with a changed name (to not use chocolatey). See the restrictions under https://docs.chocolatey.org/en-us/create/create-packages#naming-your-package.
David
chocolatey-ops (reviewer) on 15 Aug 2023 11:05:23 +00:00:
We've found chocolatey-sendmouseclick.extension v1.0.0 in a submitted status and waiting for your next actions. It has had no updates for 20 or more days since a reviewer has asked for corrections. Please note that if there is no response or fix of the package within 15 days of this message, this package version will automatically be closed (rejected) due to being stale.
Take action:
If your package is failing automated testing, you can use the chocolatey test environment to manually run the verification and determine what may need to be fixed.
Note: We don't like to see packages automatically rejected. It doesn't mean that we don't value your contributions, just that we can not continue to hold packages versions in a waiting status that have possibly been abandoned. If you don't believe you will be able to fix up this version of the package within 15 days, we strongly urge you to log in to the site and respond to the review comments until you are able to.
foundata (maintainer) on 19 Aug 2023 17:06:49 +00:00:
Hi David,
I don't know how we missed this rule (as we really read the linked page upfront). I can only guess there was some mental anchoring because of existing packages like chocolatey-fastanswers.extension.
Sorry for the circumstances. We will self-reject, rename, test and resubmit.
Cheers,
Andreas
foundata (maintainer) on 19 Aug 2023 17:54:51 +00:00:
Hi David,
small question: would it be ok to simply drop the "chocolatey-" prefix at all and just use "sendmouseclick.extension"? Adding "choco-inofficial-" feels a bit cumbersome.
Cheers,
Andreas
TheCakeIsNaOH (reviewer) on 19 Aug 2023 18:04:49 +00:00:
Using
sendmouseclick.extensionsounds good to me.Regards, TheCakeIsNaOH
Status Change - Changed status of package from 'submitted' to 'rejected'.
foundata (maintainer) on 19 Aug 2023 23:57:58 +00:00:
Hi TheCakeIsNaOH,
hi David,
I resubmitted the packages without the prefix:
Thanks again for explaining the issue, your time and efforts and sorry again for such an obvious, avoidable mistake on my side.
Cheers,
Andreas