When application starts after talon, the scope is wrong

[PetrKryslUCSD]

On Windows 10: when an application is started at the point where Talon is already running, often the scope is that of the previously active window. Sometimes switching applications will correct the issue, sometimes one has to restart Talon for the scope to be correct.

[lunixbochs]

I just fixed a bug related to this in beta 592, please confirm whether the issue appears after that version

[PetrKryslUCSD]

Looks good! Many thanks. P

[PetrKryslUCSD]

Spoke to soon. The error still persists.

[lunixbochs]

does the new application show up in ui.apps() in the repl?
does the new window show up in ui.windows()?
is the right window active for the app, if you find the app in ui.apps() and check app.active_window?
is this related to specific apps each time, or if you launch a random app like notepad does it also have the issue?

[AndreasArvidsson]

• yes
• yes
• no: Window(None) is the active window. app.windows shows the correct window as the first item though
• Seems to happen with different applications, but doesn't happen every time. If I restart Talon multiple times sometimes there is a problem and sometimes not. Notepad is one of the applications I've had problems with but also firefox for example.

beta 596
windows 11

[PetrKryslUCSD]

Just happened again. 596, Win 11.

The application is SublimeMerge.

[PetrKryslUCSD]

Switching applications a few times and checking the scope again: now it is correct.

[dgrunwald]

I frequently have this issue with a newly started windows terminal (the modern app; on Windows 10). Just had it again with 0.3.1-596-ge72c.
Switching focus to another app and back to Windows terminal is almost always sufficient as a workaround; though very rarely I had to restart talon (but the last time that happened was a couple versions ago).

[mirober]

I've very occasionally run into the same thing but have never been able to find a reliable repro for it. One thing that seems to be able to trigger it is launching applications from the path bar of a file explorer window. This only triggers the bug sometimes though and usually only the first time after a restart. Just tried it on the latest beta and got this:

The imgui window is showing:

    gui.text(f"{ui.active_app()}")
    gui.text(f"{ui.active_app().exe}")
    gui.text(f"{ui.active_window().title}")
    gui.text(f"{GetForegroundWindow()}")
    gui.text(f"{GetWindowText(GetForegroundWindow())}")
    gui.text(f"{GetWindowText(ui.active_window().id)}")

This may be a separate issue to the OP.

[lunixbochs]

try again on 597

[AndreasArvidsson]

I've been trying to recreate the problem and can't anymore. That could mean that it's fixed or that it has just become more seldom since it was intermittent before, but so far so good!