@Andreas_Hegenberg I don't know exactly when it started. Recently. I have different shortcuts in different apps that trigger completely different things. Normally they work well. But suddenly they stopped working.
What I then have to do is bring the BTT configuration window to the foreground, close it (or restart BTT, but that's not necessary) and go back to the other app.
I've tried leaving the BTT window open all the time, but that doesn't help.
I certainly don't want to put you to the trouble of looking for this strange error, but maybe you have a general idea? Thanks!
I would say in about 30% of cases the shortcut does not work.
And I really only mean this shortcut. For example ⌃+c. If I choose ⌃+a instead, it always works. This probably makes troubleshooting even more complicated. Why should a shortcut only work sometimes?
I change the shortcuts wherever I can. That's the easiest solution. Maybe it's just a problem with my configuration. So don't waste any more time on this
I'm not sure if this is somehow related, but for me since few updates a particular shortcut stops (meaning it is working and then all the sudden it stops) working (however triggered/shown in "Recently Used") is not working unless I restart BTT. I think this happens most often after Sleep.
are you sure it’s not just the condition that enters the unexpected path? If it is shown in recently used, BTT does start the action sequence - so it’s at least not an issue with the keyboard shortcut
The checked width is off by one in your two shortcuts
It should not. I mean the action should fall under the "Else" statement because the windows I'm trying to move have different focused_window_width and focused_window_height than the ones specified in the "If" condition:
Additionally this happens sporadic, I'm not changing window's size and all of the sudden I cannot move it to the left monitor. I'm not sure if the following logs will be useful since they are the same for the working trigger/action, but still:
2025/02/25 12:53:48:060|NOTCH|S5|
2025/02/25 12:53:51:535|ASL|performing 47|
2025/02/25 12:53:51:535|ASL|triggering action Move Window to Next Monitor - 64F0E2E8-F7EA-418A-A76A-25740B1152BA|
2025/02/25 12:53:51:551|ASL|performing 334|
2025/02/25 12:53:51:551|ASL|triggering action END If Condition - 4DD9E410-47E1-4949-8C60-39E9E3B29F86|
2025/02/25 12:53:51:551|ASL|already 8|
I've just tested that if the conditions are evaluated to true than the actions under the IF are executed successfully. - resulting in moving the window to the left screen with the specified configuration:
I have recently worked on a more reliable way to get the focused window in some special situations. Not sure if that would help you, but it's included in 5.225.
Your setup is fine as the action has been triggered (when that log is written, nothing can stop the action execution anymore). So the issue must be with the action that is being triggered.
One thing to note (BTT shows a warning about this when first using that action):
The move window to next monitor action only works if both monitors have the same resolution.
Thanks for this Andreas, this is good to know, however I guess this is not the issue since my both monitors have the same resolution + it is working and at some point it stops + if I restart BTT it starts working again.
I'll try 5.225 or newer version (when available), hope it will be fixed. Just a note - BTT is able to get the focused window since if I try to execute another trigger/action it is working fine on this window (e.g. to maximize it).
In general the "Move Window To Next Monitor" action is very old (was one of the first things added to BTT 15 years ago) and relies on some pretty old code paths. It might be worth switching to the "Custom Move / Resize" action - maybe I can switch that action to make use of this more modern code.
