Make Screen.find support multiple monitors

[comcaptain]

Short overview
According to doc of Screen.find and my experiment, search can only be done in the main monitor

Use case
It would be very convenient if Screen.find can work on multiple monitors

[fadhilx]

is there any news for this?

[svettwer]

Hiho 👋

Nope, no news. I'm using a dual monitor setup where screen.find works great. Maybe it depends on the window/desktop manager?! Some more information about the setup of @comcaptain would be nice for evaluation. But we're also always happy to receive PRs. 🎉

[github-actions]

This issue is stale because it has been open for 30 days with no activity.

[s1hofmann]

Still open

[github-actions]

This issue is stale because it has been open for 30 days with no activity.

[github-actions]

This issue is stale because it has been open for 30 days with no activity.

[github-actions]

This issue was closed because it has been inactive for 14 days since being marked as stale.

[raphaelmenges]

I believe the same limitation applies for Screen.grabRegion? At least on macOS.

[s1hofmann]

I believe the same limitation applies for Screen.grabRegion? At least on macOS.

Correct

[raphaelmenges]

Looking forward for this feature. I have even taken the effort to port the captureScreen function of RobotJS to node-addon-api for the mean time, since that works for my multi-monitor setup: raphaelmenges/robotjs@da27b52

[s1hofmann]

Capturing all monitors at once is actually doable, the reason why I've limited it to the main screen for now is that I need to spend some time to investigate how to handle screen coordinates consistently across the different window systems to properly work with scale settings, sorting etc.

I prefer a limited but consistent setup over something that could work by accident.

But as long as I don't have enough sponsorships to work on it full time it will take a while to land this, as I'm quite limited with my time 🙁

[raphaelmenges]

Thanks for the reply and effort!

To my understanding, the multi-monitor support of Robotjs indeed does work by accident, but it is fine so far. The different scaling and DPI handling across different systems is really a pain and I am looking forward for a sensible solution :)

[draeder]

Dropping a comment for notifications on updates to this issue.

EDIT: For MacOS these commands reveal the coordinate info I need -

defaults read /Library/Preferences/com.apple.windowserver.plist > output.txt on my MacBook Pro 2020 13" running macOS Monterey (v12.5.1). But, talking with another developer, he doesn't have that domain, but instead has: com.apple.windowserver.displays.plist.