search

jdf / Processing.py-Bugs

A home for all bugs and feature requests about Python Mode for the Processing Development Environment.
41 stars 8 forks source link

in the python version, everything is 25% bigger than what must be #360

Closed Aria-AAs closed 2 years ago

Aria-AAs commented 2 years ago

I noticed this size conflict and low accuracy in the python version a few months ago and made an issue for it, but after that I got sick and I was in the hospital for about one month anyway the issue is still alive so I look at it more accurate and noticed that that size conflict has a ratio and try to find it and as you can see its 25% I used an application called "Snagit" to see how many pixels are on the screen captured by the application. java version with 800x800 size: java_800 python version with 800x800 size: (as you can see it captured 1000x1000 pixels.) python_800 java version with 400x400 size: java_400 python version with 400x400 size: (as you can see it captured 500x500 pixels.) python_400 java version with 100x100 size: java_100 python version with 100x100 size: (as you can see it captured 125x125 pixels.) python_100

tabreturn commented 2 years ago

It seems the Windows display scale settings can lead to these types of issues. But the save() function creates an image of the proper size regardless of the display scale: https://github.com/jdf/Processing.py-Bugs/issues/353

Also: there are issues with Processing 4 and Python Mode. Use Processing 3.5.4 for now.