-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
problems with "processing python" #208
Comments
It seems the Python display window zoomed/scaled, to ~10% or so larger, is making everything look bad. I couldn't replicate this on my computer. It's a long shot -- but maybe this is some leftover config messing around with your Processing? What if you delete your preferences file (listed at the bottom of the File > Preferences panel), reopen Processing, and then try rerun a Python sketch? |
I deleted the preferences file and test again but everything is the same as before looks bad |
maybe because python is a bit slower than java that's why the precision is looking like that |
I find it relevant to the windows display scale setting and I hope the developers fix it as soon as possible |
Hello, I'm new to processing and also new to programming. I just know a bit of C++ and python.
I was trying to convert a java base code in processing to python so that I can work on it better but there was something that takes my attention.
I write a same code in java and python in processing but their output is not the same in visual.
python version is a little bigger and also less accurate in drawing things like circles and lines.
I put an example here for you to see what is my mean.
this is the code:
python:
def setup():
size(500, 500)
def draw():
circle(mouseX, mouseY, 50)
java:
void setup() {
size(500, 500);
}
void draw() {
circle(mouseX, mouseY, 50);
}
and this is the outputs:
Am I doing something wrong or is kind of normal that the python version is like this?
I also see that the python version doesn't have debugging mode and the auto-formatting doesn't work on python.
The text was updated successfully, but these errors were encountered: