部分应用程序窗口定位功能失效问题求助

Hey there! Let's dive into why your window positioning code might be failing for some apps (like Chrome) and work through fixes step by step.

1. Fix Redundant Flags in SetWindowPos #

First, I spotted a small typo in your flags: you included SWP_NOZORDER twice. It’s harmless but unnecessary—clean it up to avoid confusion:

SetWindowPos(handle, IntPtr.Zero, 0, 0, 0, 0, SWP_NOZORDER | SWP_NOSIZE);

2. Validate the Target Window Handle #

Not every "chrome" process corresponds to the main browser window—Chrome spawns helper processes for tabs, extensions, and background tasks. Add checks to ensure you’re targeting a valid, visible window:

if (process.ProcessName.Contains("chrome") 
    && process.MainWindowHandle != IntPtr.Zero 
    && !string.IsNullOrEmpty(process.MainWindowTitle))
{
    // Proceed with positioning logic
}

This skips empty handles and background processes that don’t have a visible window.

3. Handle DPI Scaling Issues #

Modern Windows apps use DPI scaling, which means logical pixels (what your code uses) might not map directly to physical screen pixels. If your app isn’t DPI-aware, the coordinates you pass to SetWindowPos will be scaled incorrectly.

Fix: Enable DPI Awareness #

Add an app.manifest file to your project with this section:

<application xmlns="urn:schemas-microsoft-com:asm.v3">
    <windowsSettings>
        <dpiAware xmlns="http://schemas.microsoft.com/SMI/2005/WindowsSettings">true/PM</dpiAware>
    </windowsSettings>
</application>

Or set it programmatically at startup:

[DllImport("user32.dll")]
private static extern bool SetProcessDpiAwarenessContext(int dpiFlag);

// Call this early in your app
SetProcessDpiAwarenessContext(-4); // Enables per-monitor DPI awareness v2

4. Overcome Foreground Window Restrictions #

Windows has strict rules about which apps can take focus (to prevent malicious software from hijacking the screen). SetForegroundWindow might fail if your app doesn’t have the necessary permissions.

Fix: Use AttachThreadInput to Gain Focus Access #

Modify your code to attach to the target window’s thread, which lets you safely bring it to the foreground:

[DllImport("user32.dll")]
private static extern IntPtr GetWindowThreadProcessId(IntPtr hWnd, IntPtr lpdwProcessId);

[DllImport("kernel32.dll")]
private static extern IntPtr GetCurrentThreadId();

[DllImport("user32.dll")]
private static extern bool AttachThreadInput(IntPtr idAttach, IntPtr idAttachTo, bool fAttach);

// Inside your loop:
IntPtr currentThread = GetCurrentThreadId();
IntPtr targetThread = GetWindowThreadProcessId(handle, IntPtr.Zero);

// Attach to the target thread to gain focus permission
AttachThreadInput(currentThread, targetThread, true);
SetForegroundWindow(handle);
AttachThreadInput(currentThread, targetThread, false);

5. Handle App-Specific Window States #

Some apps (like Chrome in maximized or fullscreen mode) might ignore manual positioning until restored to a normal window state. Add a check to restore the window first:

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

const int SW_RESTORE = 9;

// Before setting position:
ShowWindow(handle, SW_RESTORE);

Final Modified Code #

Putting all these fixes together, here’s an improved version of your code:

using System;
using System.Diagnostics;
using System.Runtime.InteropServices;
using System.Windows.Forms;

class WindowPositioner
{
    [DllImport("user32.dll")]
    private static extern bool SetForegroundWindow(IntPtr hWnd);

    [DllImport("user32.dll")]
    private static extern bool SetWindowPos(IntPtr hWnd, IntPtr hWndInsertAfter, int X, int Y, int cx, int cy, uint uFlags);

    [DllImport("user32.dll")]
    private static extern IntPtr GetWindowThreadProcessId(IntPtr hWnd, IntPtr lpdwProcessId);

    [DllImport("kernel32.dll")]
    private static extern IntPtr GetCurrentThreadId();

    [DllImport("user32.dll")]
    private static extern bool AttachThreadInput(IntPtr idAttach, IntPtr idAttachTo, bool fAttach);

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

    [DllImport("user32.dll")]
    private static extern bool SetProcessDpiAwarenessContext(int dpiFlag);

    private const uint SWP_NOZORDER = 0x0004;
    private const uint SWP_NOSIZE = 0x0001;
    private const int SW_RESTORE = 9;

    static void Main()
    {
        // Enable DPI awareness first
        SetProcessDpiAwarenessContext(-4);

        Process[] processes = Process.GetProcesses();
        foreach (var process in processes)
        {
            Console.WriteLine("Process Name: {0} ", process.ProcessName);
            if (process.ProcessName.Contains("chrome") 
                && process.MainWindowHandle != IntPtr.Zero 
                && !string.IsNullOrEmpty(process.MainWindowTitle))
            {
                IntPtr handle = process.MainWindowHandle;

                // Restore window if maximized
                ShowWindow(handle, SW_RESTORE);

                // Gain permission to set foreground
                IntPtr currentThread = GetCurrentThreadId();
                IntPtr targetThread = GetWindowThreadProcessId(handle, IntPtr.Zero);
                AttachThreadInput(currentThread, targetThread, true);
                SetForegroundWindow(handle);
                AttachThreadInput(currentThread, targetThread, false);

                // Move window to (0,0)
                bool success = SetWindowPos(handle, IntPtr.Zero, 0, 0, 0, 0, SWP_NOZORDER | SWP_NOSIZE);
                Console.WriteLine($"Positioning success for {process.MainWindowTitle}: {success}");
            }
        }
        MessageBox.Show("Operation completed");
    }
}

Additional Notes #

• Admin Permissions: If the target app runs as administrator, your app must also run as admin to modify its window.
• UWP Apps: Universal Windows Platform apps won’t respond to SetWindowPos—use the ApplicationView API from the Windows Runtime instead.

内容的提问来源于stack exchange，提问作者thompogi