"Trigger On Change Of Advanced Trigger Condition" is triggered unexpectedly

Bugs or Unexpected Behavior
1

Based on this where I've setup the below:

image
image2698×750 320 KB

which is working, however the issue that once I move MS Edge to the right monitor the trigger is triggered. If I move the window to the left monitor it is not triggered. I'm moving the window with this:

image
image2648×934 478 KB

2

During move resize the window dimensions can not be received correctly, however this should not cause issues in your scroll modifier scenario because while moving the window you wouldn't scroll anyways

3

Yep, no real issue with the scroll modifier. The issue is only that "Trigger On Change Of Advanced Trigger Condition" is triggered unexpectedly, but now I get why this is:

During move resize the window dimensions can not be received correctly

Thank you.

4

Andreas, it seems this (moving MS Edge window) is not the only time this is being triggered. If I click on some of the icons in the menu bar it is again triggered. Initially I tough that the reason is the more "fancy/modern" pop-up shown are causing this, but I'm not sure anymore. Here what I mean by "fancy/modern":

image
image672×364 40.6 KB

OR

image
image528×440 35.5 KB

OR even a default macOS one:

image
image700×200 57.8 KB

and here's a some which are not triggering it:

image
image412×306 55.5 KB

OR

image
image986×242 49.9 KB

image
image474×248 56.7 KB

Do you have idea for this?

5

Does your condition only check the X value? In that case it would trigger in many cases unless you make it more specific. I'd at least add an active app check and also include the y value

6

This trigger is already configured under MS Edge and it is triggered only when Edge is active:

image
image2648×1272 480 KB

7

even then, the x position being less than 288 would also apply for the menubar and dock items that are less than 288px away from the window origin. I'd add a condition to either check the hovered window or include the y position.

8

The trigger is only triggered for some menu bar icons only when I click on them (the original behavior also works - mouse hovering the vertical tabs) and they are not not near to the vertical tabs/to the 288px. Here's a screenshot:

image
image1804×1188 277 KB

I've just noticed that this also happen when I open the MS Edge QuicKey extension using a shortcut (not configured in BTT), this only happens when using the shortcut not when I click on the plug icon

image
image1744×1300 254 KB

In the "recently used":

image
image1426×1606 353 KB

the entry marked in red is appearing right after I invoke the QuicKey or click on some of the the menu bar icons.

9

It can also happen if the reference window changes (like for the quick keys) and possibly for some menubar icons. Even if it doesn't look like a separate window, such stuff is often implemented as window and hovering it will make it the reference for the condition. Even every menubar status item is internally implemented as a window.

That's why I mentioned checking the hovered window, but you'd need to find some condition that identifies a real edge window. I'll install Edge later and try it :slight_smile: Do you like Edge better than Safari?

10

Appreciate this Andreas. I've ended up using mouse_position_x, since Edge is almost always on the left screen and maximized.

I've prefer Edge and Firefox over Safari due to few reasons (no particular order):

  1. I'm used to them.
  2. They have more extensions available - QuicKey is a must for me + Vimium (maybe there are some other alternatives for Safari, but I'm not sure)
  3. Split view
  4. Vertical tabs (I'm aware that in Safari you can have similar, but you still have the regular horizontal tabs)
  5. I'm Android user and I can easily sync tabs between my phone and my Edge/Firefox no matter where they are installed