Skip to content
This repository has been archived by the owner on Jun 10, 2018. It is now read-only.

screen.get_color always returns 0 #54

Closed
Archi73ct opened this issue Jul 15, 2014 · 8 comments
Closed

screen.get_color always returns 0 #54

Archi73ct opened this issue Jul 15, 2014 · 8 comments
Labels

Comments

@Archi73ct
Copy link

Im trying to detect the color at at special point, however trying to use screen.get_color(x,y) just returns a 0 when i was expecting a hexidecimal, is there a fix for this?

@msanders msanders added the bug label Nov 6, 2014
@Haimrik
Copy link

Haimrik commented Jan 21, 2015

I also have the same bug. Also, when I use autopy.bitmap.capture_screen it returns a black image.
Did you find any solution?

@swisscheez
Copy link

seeing same here - any fix for this? using a win 64 machine if that matters.

@yasinyazici
Copy link

@msanders I've the same problem.

@potpath
Copy link

potpath commented Mar 21, 2015

For Mac OS X, this problem is solved on this fork https://github.com/staydecent/autopy.
To successfully build this fork with clang, see 5cd3349 from https://github.com/potpath/autopy.

@ktsalik
Copy link

ktsalik commented Dec 26, 2015

+1 got the exact same issue

@stevebasher
Copy link

+1 Still getting this issue, using El Capitain on Mac.

@georgehipp
Copy link

On Windows with autopy3 replacing autopy3.screen.get_color() with autopy3.bitmap.capture_screen().get_color seems to circumvent the issue in my case.
Example:

autopy3.color.hex_to_rgb(autopy3.screen.get_color(500,500))
(0, 0, 0) - Wrong
autopy3.color.hex_to_rgb(autopy3.bitmap.capture_screen().get_color(500,500))
(247, 247, 247) - Correct

@msanders
Copy link
Collaborator

msanders commented May 2, 2018

This should be fixed now in the latest version.

@msanders msanders closed this as completed May 2, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

10 participants