This "bug" comes up a few times a year, where users find that their calculated coordinates seem to be no-sensical on their actual screen sizes. This is just due to higher pixel density on retina display macs. This has an easy work around of dividing x and y coordinates by 2. I explored ways to automate checks for whether retina display was present but didn't want to add any additional dependencies to the project or risk breaking projects that use the existing work around. I've just added a warning to the doc-string of the size() function in innit.py warning users that if they are using a retina display mac book, they can expect a pixel density of 2x2, meaning they will most likely have to divide x and y coordinates by 2 to get their desired position. This way there is an official notice in the project so that people don't keep posting it as an issue here.
This "bug" comes up a few times a year, where users find that their calculated coordinates seem to be no-sensical on their actual screen sizes. This is just due to higher pixel density on retina display macs. This has an easy work around of dividing x and y coordinates by 2. I explored ways to automate checks for whether retina display was present but didn't want to add any additional dependencies to the project or risk breaking projects that use the existing work around. I've just added a warning to the doc-string of the size() function in innit.py warning users that if they are using a retina display mac book, they can expect a pixel density of 2x2, meaning they will most likely have to divide x and y coordinates by 2 to get their desired position. This way there is an official notice in the project so that people don't keep posting it as an issue here.