Unpacking Software Livestream

Join our monthly Unpacking Software livestream to hear about the latest news, chat and opinion on packaging, software deployment and lifecycle management!

Learn More

Chocolatey Product Spotlight

Join the Chocolatey Team on our regular monthly stream where we put a spotlight on the most recent Chocolatey product releases. You'll have a chance to have your questions answered in a live Ask Me Anything format.

Learn More

Chocolatey Coding Livestream

Join us for the Chocolatey Coding Livestream, where members of our team dive into the heart of open source development by coding live on various Chocolatey projects. Tune in to witness real-time coding, ask questions, and gain insights into the world of package management. Don't miss this opportunity to engage with our team and contribute to the future of Chocolatey!

Learn More

Calling All Chocolatiers! Whipping Up Windows Automation with Chocolatey Central Management

Webinar from
Wednesday, 17 January 2024

We are delighted to announce the release of Chocolatey Central Management v0.12.0, featuring seamless Deployment Plan creation, time-saving duplications, insightful Group Details, an upgraded Dashboard, bug fixes, user interface polishing, and refined documentation. As an added bonus we'll have members of our Solutions Engineering team on-hand to dive into some interesting ways you can leverage the new features available!

Watch On-Demand
Chocolatey Community Coffee Break

Join the Chocolatey Team as we discuss all things Community, what we do, how you can get involved and answer your Chocolatey questions.

Watch The Replays
Chocolatey and Intune Overview

Webinar Replay from
Wednesday, 30 March 2022

At Chocolatey Software we strive for simple, and teaching others. Let us teach you just how simple it could be to keep your 3rd party applications updated across your devices, all with Intune!

Watch On-Demand
Chocolatey For Business. In Azure. In One Click.

Livestream from
Thursday, 9 June 2022

Join James and Josh to show you how you can get the Chocolatey For Business recommended infrastructure and workflow, created, in Azure, in around 20 minutes.

Watch On-Demand
The Future of Chocolatey CLI

Livestream from
Thursday, 04 August 2022

Join Paul and Gary to hear more about the plans for the Chocolatey CLI in the not so distant future. We'll talk about some cool new features, long term asks from Customers and Community and how you can get involved!

Watch On-Demand
Hacktoberfest Tuesdays 2022

Livestreams from
October 2022

For Hacktoberfest, Chocolatey ran a livestream every Tuesday! Re-watch Cory, James, Gary, and Rain as they share knowledge on how to contribute to open-source projects such as Chocolatey CLI.

Watch On-Demand

Downloads:

39

Downloads of v 1.0.0:

39

Last Update:

03 Jun 2023

Package Maintainer(s):

Software Author(s):

  • foundata

Tags:

chocolatey-usewindow.extension focus window non-silent user32.dll

Chocolatey Use-Window extension (helper to focus a window)

Downloads:

39

Downloads of v 1.0.0:

39

Maintainer(s):

Software Author(s):

  • foundata

Chocolatey Use-Window extension (helper to focus a window)

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


Validation Testing Passed


Verification Testing Passed

Details

Scan Testing Successful:

No detections found in any package files

Details
WARNING

This package was rejected on 19 Aug 2023. The reviewer TheCakeIsNaOH has listed the following reason(s):

foundata (maintainer) on 03 Jun 2023 20:39:22 +00:00:

User 'foundata' (maintainer) submitted package.

chocolatey-ops (reviewer) on 03 Jun 2023 21:10:31 +00:00:

chocolatey-usewindow.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.

  • ProjectUrl and ProjectSourceUrl are typically different, but not always. Please ensure that projectSourceUrl is pointing to software source code or remove the field from the nuspec. More...
  • Release Notes (releaseNotes) are a short description of changes in each version of a package. Please include releasenotes in the nuspec. NOTE: To prevent the need to continually update this field, providing a URL to an external list of Release Notes is perfectly acceptable. More...
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.

  • The package maintainer field (owners) matches the software author field (authors) in the nuspec. The reviewer will ensure that the package maintainer is also the software author. More...

chocolatey-ops (reviewer) on 03 Jun 2023 21:14:58 +00:00:

chocolatey-usewindow.extension has passed automated package testing (verification). The next step in the process is package scanning.
Please visit https://gist.github.com/choco-bot/3e3dd7fa4ce018f5e105c4086c5158d9 for details.
This is an FYI only. There is no action you need to take.

chocolatey-ops (reviewer) on 03 Jun 2023 21:25:02 +00:00:

chocolatey-usewindow.extension has passed automated virus scanning.

foundata (maintainer) on 03 Jun 2023 21:48:41 +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:

chocolatey-usewindow.extension exists for sharing the "find window, bring it to the front and focus it"-part as we split sending keystrokes and mouse clicks to keep it easy to use, modular and small.

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:03:10 +00:00:

  • We do not plan to create a dedicated website for this extension yet, therefore the ProjectUrl and ProjectSourceUrl are the same. It makes sense to send users to the repository, showing the rendered README.md at 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.
  • releaseNotes will be filled out (pointing to CHANGELOG.md) on the first update.

TheCakeIsNaOH (reviewer) on 19 Aug 2023 16:24:29 +00:00:

Hi,

Community packages should not have "chocolatey" in their ID or title, see the naming conventions: https://docs.chocolatey.org/en-us/create/create-packages#naming-your-package

I'll reject this package as an invalid name, please resubmit under a different name.

Regards, TheCakeIsNaOH
Status Change - Changed status of package from 'submitted' to 'rejected'.

foundata (maintainer) on 19 Aug 2023 17:07:59 +00:00:

Hi TheCakeIsNaOH,

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 rename, test and resubmit.

Cheers,
Andreas

TheCakeIsNaOH (reviewer) on 19 Aug 2023 17:26:35 +00:00:

Sounds good.
There are quite a few packages grandfathered in using chocolatey in their ID, as they where created before that naming rule came into effect.
Regards, TheCakeIsNaOH

foundata (maintainer) on 19 Aug 2023 23:58:23 +00:00:

Hi TheCakeIsNaOH,

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

Description

A Chocolatey extension providing helper functions for querying and focusing windows. These functions may be used in Chocolatey install and uninstall scripts by declaring this package a dependency in your package's .nuspec.

The most important function is Use-Window, which is able to focus a window and bring it to the front. A script can easily switch between windows this way.


extensions\chocolatey-usewindow.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\Find-WindowHandle.ps1
function Find-WindowHandle {
    <#
    .SYNOPSIS
        Finds the handle of the window matching the given query. Returns an
        IntPtr matching the given query if a window is found or IntPtr.Zero
        otherwise.

    .PARAMETER Query
        A query that has one of the following formats:

        - A RegEx pattern that is tested against all existing windows.
        - A window handle.
        - A window title followed by its handle enclosed in parentheses.

    .EXAMPLE
        Find the handle of the first window having "powershell" somewhere
        in its name:

            Find-WindowHandle 'powershell'

    .EXAMPLE
        Find the handle of the first window named exactly "powershell":

            Find-WindowHandle '^powershell$'

    .EXAMPLE
        Return the given handle, if a window exists with this handle:

            Find-WindowHandle 10101010

    .EXAMPLE
        Return the given handle, if a window exists with the handle at the
        end of the given string:

            Find-WindowHandle 'powershell (10101010)'

    #>
    Param(
        [Parameter(Mandatory = $True,
                   HelpMessage = 'A RegEx pattern that is tested against all existing windows OR a window handle OR a window title followed by its handle enclosed in parentheses.')]
        [String]$Query
    )

    # find handle in title (either the whole title is the handle, or enclosed in parenthesis)
    if ($Query -match '^\d+$') {
        $Handle = [IntPtr]::new($Query)
    } elseif ($Query -match '^.+ \((\d+)\)\s*$') {
        $Handle = [IntPtr]::new($Matches[1])
    } else {

        # find handle in existing processes.
        $MatchingWindows = [UseWindowHelpers]::GetAllExistingWindows() | ? { $PSItem.Key -match $Query }

        if (-not $MatchingWindows) {
            return [IntPtr]::Zero
        }

        # no need to ensure the window does exist, return immediately
        return $MatchingWindows[0].Value
    }

    # make sure the handle exists
    if ([UseWindowHelpers]::WindowExists($Handle)) {
        return $Handle
    } else {
        return [IntPtr]::Zero
    }
}
extensions\Helper.ps1
Add-Type -Language 'CSharp' -ReferencedAssemblies @('System', 'System.Runtime.InteropServices') -TypeDefinition @"
    using System;
    using System.Collections.Generic;
    using System.Runtime.InteropServices;
    using System.Text;

    public static class UseWindowHelpers
    {
        [DllImport("user32.dll")]
        [return: MarshalAs(UnmanagedType.Bool)]
        private static extern bool SetForegroundWindow(IntPtr hWnd);

        [DllImport("user32.dll")]
        [return: MarshalAs(UnmanagedType.Bool)]
        private static extern bool ShowWindow(IntPtr hWnd, int nCmdShow);

        public static void BringToFront(IntPtr handle)
        {
            ShowWindow(handle, 5);
            SetForegroundWindow(handle);
        }


        [DllImport("user32.dll")]
        [return: MarshalAs(UnmanagedType.Bool)]
        private static extern bool GetWindowRect(IntPtr hWnd, out RECT lpRect);

        [StructLayout(LayoutKind.Sequential)]
        private struct RECT
        {
            public int Left, Top, Right, Bottom;
        }

        public static bool WindowExists(IntPtr handle)
        {
            RECT r;

            return GetWindowRect(handle, out r);
        }

        private delegate bool EnumDesktopWindowsDelegate(IntPtr hWnd, int lParam);

        [DllImport("user32.dll")]
        private static extern bool EnumDesktopWindows(IntPtr hDesktop, EnumDesktopWindowsDelegate lpfn, IntPtr lParam);

        [DllImport("user32.dll")]
        private static extern int GetWindowText(IntPtr hWnd, StringBuilder lpWindowText, int nMaxCount);

        public static List<KeyValuePair<string, IntPtr>> GetAllExistingWindows()
        {
            var windows = new List<KeyValuePair<string, IntPtr>>();

            EnumDesktopWindows(IntPtr.Zero, (h, _) =>
            {
                StringBuilder title = new StringBuilder(256);
                int titleLength = GetWindowText(h, title, 512);

                if (titleLength > 0)
                    windows.Add(new KeyValuePair<string, IntPtr>(title.ToString(), h));

                return true;
            }, IntPtr.Zero);

            return windows;
        }
    }
"@
extensions\Use-Window.ps1
function Use-Window {
    <#
    .SYNOPSIS
        Focuses the window having the given handle and brings it to the front.

    .PARAMETER Query
        A window title query that will be resolved using "Find-WindowHandle".

    .EXAMPLE
        Focus the first window having "powershell" somewhere in its name and
        bring it to the front:

            Use-Window "powershell"

    .EXAMPLE
        Focus the first window named exactly "powershell" and bring it to the
        front:

            Use-Window'^powershell$'
    #>
    Param(
        [Parameter(Mandatory = $True,
                   ValueFromPipeline = $True,
                   HelpMessage = 'A window title query that will be resolved using "Find-WindowHandle".')]
        [ValidateScript({
            if ( (Find-WindowHandle $PSItem) -eq 0 ) {
                Throw "Use-Window: Cannot find window handle for query '${PSItem}'."
            } else {
                $True
            }
        })]
        [String]$Query
    )

    $Handle = Find-WindowHandle $Query

    [UseWindowHelpers]::BringToFront($Handle)
}

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.

Add to Builder Version Downloads Last Updated Status

This package has no dependencies.

Discussion for the Chocolatey Use-Window extension (helper to focus a window) Package

Ground Rules:

  • This discussion is only about Chocolatey Use-Window extension (helper to focus a window) and the Chocolatey Use-Window extension (helper to focus a window) 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 Use-Window extension (helper to focus a window), 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