You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In element-based nav mode (first introduced in #1), Scoot will find all elements in the focused window of the frontmost app.
It would be better if Scoot could find all elements that are on all attached screen(s), across all apps.
Of course, windows can overlap, and we'll need to ignore any elements that are fully occluded by a window above it.
AXUIElementCopyElementAtPosition will find an element at the specific coordinate (if one exists), but you need to pass it an application reference, so it is not directly usable in this context (and, regardless, checking every possible x,y value on every screen seems wasteful from a performance perspective).
https://stackoverflow.com/a/56941105/ has some code that might be helpful (finding all windows on the screen, and ordering them relative to each other).
The text was updated successfully, but these errors were encountered:
It would be better if Scoot could find all elements that are on all attached screen(s), across all apps.
A stepping stone could be finding all elements in the window that is under the mouse cursor (if it differs from the focused window of the frontmost app). Of course, there's still occlusion issues to deal with.
In element-based nav mode (first introduced in #1), Scoot will find all elements in the focused window of the frontmost app.
It would be better if Scoot could find all elements that are on all attached screen(s), across all apps.
Of course, windows can overlap, and we'll need to ignore any elements that are fully occluded by a window above it.
AXUIElementCopyElementAtPosition
will find an element at the specific coordinate (if one exists), but you need to pass it an application reference, so it is not directly usable in this context (and, regardless, checking every possible x,y value on every screen seems wasteful from a performance perspective).https://stackoverflow.com/a/56941105/ has some code that might be helpful (finding all windows on the screen, and ordering them relative to each other).
The text was updated successfully, but these errors were encountered: