I use Astropad Studio with a Luna Display USB-C dongle.
On the remote MacBook Pro M1 I try to use a named trigger with an extended condition "mouse_pos_percent_y" or "mouse-pos_y. On the configuration window it tells me in both cases "Currently True" when i move the mouse cursor to the corresponding position (in my case the bottom) but the event never fires in the corresponding automation. To test this I used a HUD Overlay as well.
i think there is a misunderstanding of what trigger conditions are. They are evaluated once the named trigger is triggered and then decide whether the actions are executed. However the named trigger needs to be triggered by something else
OK, thank you for this information!
But can I trigger something when the mouse cursor reaches a position or side on the screen similar to the trigger condition I described?
Thank you!
Unfortunately this is not what I need. I need a pixel-accurate way to query the mouse cursor, because Luna addresses the bottom edge incorrectly with + 1 pixel.
Ah, sorry, I don't know what you could do then. It would need an action that virtually changes the edge of the screen, for example. Maybe you can do that. In any case, the advanced conditions are useless because that is not a trigger.
Edit: What if the normal trigger “Mouse to an edge” triggers the action “Move mouse” and the mouse is moved to where you want it? Does BTT then think this is the edge of the screen and trigger something? Mm, I don't know if that's understandable.
could you describe tour exact use case? I think I might know how you could set it up
Hi Andreas,
Sure. I Remote control a MacBook from an iMac with Astropad Luna. The Luna software sends a bottom cursor address with one pixel too much. For this reason, I had to subtract one pixel or set it to the exact screen height to get the dock displayed on the receiving computer. E.g.
If cursor address >= screen height + 1, then
cursor address = screen height
The Astropad guys know about this bug, but they don’t really care.
