Advanced Condition - Focused Window (Value Keeps Changing - Ruining Automation)

Bugs or Unexpected Behavior
1

Describe the bug
Hi there! Love the program. I am working on something that required the advanced condition focused_window_x & Focused_window_y.

The thing is, the values I enter, for example, are [x=2560, and y=0]

Anytime I enter in a number in the 1000s (1280, or 2560) - the trigger will WORK once, then automatically change the condition to have a comma. For example.
(1) I enter x=2560.
(2) I run the trigger.
(3) The trigger doesn't work.
(4) I check the condition.
(5) Suddenly, X=2,560 (Note the comma).
(6) The condition as a code, now only shows the first digit (x=2 instead of 2560, because of the comma being added)

Affected input device (e.g. MacBook Trackpad, Magic Mouse/Trackpad, Touch Bar, etc.):

Keyboard Bind

Device information:

  • Type of Mac: M2 Air
  • macOS version: Current Sonoma
  • BetterTouchTool version: (please post the exact version - not just "the latest one") 4.584

Additional information (e.g. crash logs, related issues, etc.):

2

This looks almost like some macOS bug. I think I have found a workaround, will be added to the next alpha tomorrow

1 Like
3

Wow thank you! I made a great workaround to window snapping that can jump monitors :slight_smile: