-
Notifications
You must be signed in to change notification settings - Fork 0
When application starts after talon, the scope is wrong #613
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I just fixed a bug related to this in beta 592, please confirm whether the issue appears after that version |
Looks good! Many thanks. P |
Spoke to soon. The error still persists. |
does the new application show up in ui.apps() in the repl? |
beta 596 |
Switching applications a few times and checking the scope again: now it is correct. |
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. |
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:
This may be a separate issue to the OP. |
try again on 597 |
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! |
I got the problem again on version 597, this time the variant where focus switching does not help. It was affecting all newly opened apps after the problem started occurring (probably when resuming from hibernation over night?), but not newly opened windows of already-running apps. |
repro'd mine on 597 |
after your repro, is there an error in your log? I found the cause for dgrunwald's and it was due to an exception |
Could a user level error in a |
ping me on slack, you might have a different issue |
no, win_title wouldn't cause this. fwiw there's a new update (599) for the general case |
With 599 I haven't been able to reproduce yet. Fingers crossed... |
closing this again, respond here if it reappears |
It happened again today. |
@PetrKryslUCSD going to DM you on the slack, there are some extra troubleshooting steps required |
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.
The text was updated successfully, but these errors were encountered: