When opening a link, the detected calling program is always the currently active window.
In the case where the process calling BrowseRouter is a background one (such as AutoHotKey for example), or if the user changes the active windows before the program make the call to BrowseRouter (if the programme lags or has an internal delay), the detected calling program is wrong...
// ----- launching on master branch with "OpenURL" profile from Visual Studio :
16/12/2024 14:27:52 BrowseRouter: Attempting to launch "example.org" for "BrowseRouter (Exécution) - Microsoft Visual Studio"
16/12/2024 14:27:52 BrowseRouter: Found URL preference "*" => "ff" ("C:\Program Files\Mozilla Firefox\firefox.exe")
16/12/2024 14:27:52 BrowseRouter: Launching C:\Program Files\Mozilla Firefox\firefox.exe with args " https://example.org"
// ----- launching on master branch with a custom autohotkey script (with Visual Studio still open)
16/12/2024 14:28:18 BrowseRouter: Attempting to launch "example.org" for "BrowseRouter (Exécution) - Microsoft Visual Studio"
16/12/2024 14:28:18 BrowseRouter: Found URL preference "*" => "ff" ("C:\Program Files\Mozilla Firefox\firefox.exe")
16/12/2024 14:28:18 BrowseRouter: Launching C:\Program Files\Mozilla Firefox\firefox.exe with args " https://example.org"
When opening a link, the detected calling program is always the currently active window.
In the case where the process calling BrowseRouter is a background one (such as AutoHotKey for example), or if the user changes the active windows before the program make the call to BrowseRouter (if the programme lags or has an internal delay), the detected calling program is wrong...