Downloads:

1,239

Downloads of v 0.70.0.1:

689

Last Update:

22 Aug 2016

Package Maintainer(s):

Software Author(s):

  • Brian Mathis

Tags:

hotkey key winhotkey

WinHotKey

0.70.0.1 | Updated: 22 Aug 2016

Downloads:

1,239

Downloads of v 0.70.0.1:

689

Maintainer(s):

Software Author(s):

  • Brian Mathis

WinHotKey 0.70.0.1

All Checks are Passing

2 Passing Test


Validation Testing Passed


Verification Testing Passed

Details

To install WinHotKey, run the following command from the command line or from PowerShell:

>

To upgrade WinHotKey, run the following command from the command line or from PowerShell:

>

To uninstall WinHotKey, run the following command from the command line or from PowerShell:

>

NOTE: This applies to both open source and commercial editions of Chocolatey.

1. Ensure you are set for organizational deployment

Please see the organizational deployment guide

  • Open Source or Commercial:
    • Proxy Repository - Create a proxy nuget repository on Nexus, Artifactory Pro, or a proxy Chocolatey repository on ProGet. Point your upstream to https://chocolatey.org/api/v2. Packages cache on first access automatically. Make sure your choco clients are using your proxy repository as a source and NOT the default community repository. See source command for more information.
    • You can also just download the package and push it to a repository Download

3. Enter your internal repository url

(this should look similar to https://chocolatey.org/api/v2)

4. Choose your deployment method:


choco upgrade winhotkey -y --source="'STEP 3 URL'" [other options]

See options you can pass to upgrade.

See best practices for scripting.

Add this to a PowerShell script or use a Batch script with tools and in places where you are calling directly to Chocolatey. If you are integrating, keep in mind enhanced exit codes.

If you do use a PowerShell script, use the following to ensure bad exit codes are shown as failures:


choco upgrade winhotkey -y --source="'STEP 3 URL'" 
$exitCode = $LASTEXITCODE

Write-Verbose "Exit code was $exitCode"
$validExitCodes = @(0, 1605, 1614, 1641, 3010)
if ($validExitCodes -contains $exitCode) {
  Exit 0
}

Exit $exitCode

- name: Ensure winhotkey installed
  win_chocolatey:
    name: winhotkey
    state: present
    version: 0.70.0.1
    source: STEP 3 URL

See docs at https://docs.ansible.com/ansible/latest/modules/win_chocolatey_module.html.

Coming early 2020! Central Managment Reporting available now! More information...


chocolatey_package 'winhotkey' do
  action    :install
  version  '0.70.0.1'
  source   'STEP 3 URL'
end

See docs at https://docs.chef.io/resource_chocolatey_package.html.


Chocolatey::Ensure-Package
(
    Name: winhotkey,
    Version: 0.70.0.1,
    Source: STEP 3 URL
);

Requires Otter Chocolatey Extension. See docs at https://inedo.com/den/otter/chocolatey.


cChocoPackageInstaller winhotkey
{
   Name     = 'winhotkey'
   Ensure   = 'Present'
   Version  = '0.70.0.1'
   Source   = 'STEP 3 URL'
}

Requires cChoco DSC Resource. See docs at https://github.com/chocolatey/cChoco.


package { 'winhotkey':
  provider => 'chocolatey',
  ensure   => '0.70.0.1',
  source   => 'STEP 3 URL',
}

Requires Puppet Chocolatey Provider module. See docs at https://forge.puppet.com/puppetlabs/chocolatey.


salt '*' chocolatey.install winhotkey version="0.70.0.1" source="STEP 3 URL"

See docs at https://docs.saltstack.com/en/latest/ref/modules/all/salt.modules.chocolatey.html.

5. If applicable - Chocolatey configuration/installation

See infrastructure management matrix for Chocolatey configuration elements and examples.

Private CDN cached downloads available for licensed customers. Never experience 404 breakages again! Learn more...

This package was approved by moderator gep13 on 02 Sep 2016.

Description

WinHotKey allows you to assign "hot keys" that do various things. Actions that can be done with a hotkey are:

  • Launch a Program
  • Open a document
  • Open a folder
  • Automatically type something (Sorry, this feature doesn't work on Vista, Windows 7, or later)
  • Control other windows on the screen

The main goal of this tool is to be easy to use. There are many other hotkey programs out there, but most of them do not provide a sufficient level of "ease of use". This walks the user through the options, while remaining a powerful tool.

When running, the program sits in the system tray. Double-clicking on the system tray icon will bring up the main window.


tools\chocolateyInstall.ps1
$packageName = 'winhotkey'
$fileType = 'exe'
$silentArgs = '/VERYSILENT /SUPPRESSMSGBOXES /NORESTART'
$url = 'http://directedge.us/files/whk/WinHotKey0.70.exe' 
Install-ChocolateyPackage $packageName $fileType $silentArgs $url -Checksum 0db56e24fbb0732cff06d7186d9a507cb026989d61d5a1e19c45497ba36b12fa -ChecksumType 'sha256'
tools\chocolateyUninstall.ps1
$packageName = 'winhotkey'
$fileType = 'exe'
$silentArgs = '/VERYSILENT /SUPPRESSMSGBOXES /NORESTART'
$scriptPath = Split-Path -parent $MyInvocation.MyCommand.Definition
$ahkFile = "$scriptPath\killwinhotkey.ahk"
$registryPath32 = 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\WinHotKey_is1'
$registryPathWow6432 = 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\WinHotKey_is1'


if (Test-Path $registryPath32) {
$registryPath = $registryPath32
}

if (Test-Path $registryPathWow6432) {
$registryPath = $registryPathWow6432
}

if ($registryPath) {
$uninstallString = (Get-ItemProperty -Path $registryPath -Name 'UninstallString').UninstallString
}

if ($uninstallString) {
Start-Process 'AutoHotkey' $ahkFile
Uninstall-ChocolateyPackage $packageName $fileType $silentArgs $uninstallString
}
tools\killwinhotkey.ahk
; wait for uninstaller to start
sleep 5000
while (true)
{
	; if uninstaller is running kill everything that has to do with winhotkey. else it opens on its own and waits to be closed.
	Process, Exist, unins000.exe
	IF (!ErrorLevel= 0)
	{
	Process, Close, WinHotKey.exe
	Process, Close, WinHotKeyCfg.exe
	sleep, 1000
	}
	else 
	{
	return
	}
}

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.

Version Downloads Last Updated Status
WinHotKey 0.70 290 Tuesday, December 30, 2014 Approved
Discussion for the WinHotKey Package

Ground Rules:

  • This discussion is only about WinHotKey and the WinHotKey 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 WinHotKey, 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.
comments powered by Disqus