# Python visual quality

**URL:** <https://discourse.processing.org/t/python-visual-quality/40360>\
**Category:** Processing.py\
**Created:** [December 29, 2022, 11:31am UTC](https://discourse.processing.org/t/python-visual-quality/40360 "2022-12-29T11:31:39Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![kmll](https://avatars.discourse-cdn.com/v4/letter/k/f4b2a3/32.png) [@kmll](https://discourse.processing.org/u/kmll)\
**Post date:** [December 29, 2022, 11:31am UTC](https://discourse.processing.org/t/python-visual-quality/40360/1 "2022-12-29T11:31:39Z")

</div>

I have tested the new version of Processing and tried the Python module. However the visual is not of the same quality as if I use Java. Is this a known issue?

```auto
def setup():
    size(800, 600)
    stroke(255)
    background(192, 64, 0)

def draw():
    line(150, 25, mouseX, mouseY)

```

**VS.**

```auto
void setup() {
  size(800, 600);
  stroke(255);
  background(192, 64, 0);
}

void draw() {
  line(150, 25, mouseX, mouseY);
}

```

---

<div class="post-metadata">

**Author:** ![Chrisir](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/chrisir/32/45_2.png) [@Chrisir](https://discourse.processing.org/u/Chrisir)\
**Post date:** [December 29, 2022, 4:40pm UTC](https://discourse.processing.org/t/python-visual-quality/40360/2 "2022-12-29T16:40:50Z")

</div>

> [@kmll](#):
>
> ```auto
> background(192, 64, 0)
> 
> ```

I would repeat that at the start of draw() in both versions, it looks more sharp

Can’t offer more to your question though

---

<div class="post-metadata">

**Author:** ![glv](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.processing.org/glv/32/18785_2.png) [@glv](https://discourse.processing.org/u/glv)\
**Post date:** [December 29, 2022, 7:58pm UTC](https://discourse.processing.org/t/python-visual-quality/40360/3 "2022-12-29T19:58:20Z")

</div>

Hello @kmll,

Python mode looks good here with Processing 3.5.4 and the windows are each 500x500.

With Processing 4.1.1 the sketch window is scaled larger for Python mode!

I do have 125% scaling on my W10 PC for displays.

 ![image](https://canada1.discourse-cdn.com/flex036/uploads/processingfoundation1/original/3X/2/d/2d1d1ba7d58c161d10ed9c99e867910b6679abdf.png)

 ![image](https://canada1.discourse-cdn.com/flex036/uploads/processingfoundation1/original/3X/8/e/8e152a312bcae9c3780b5156cfa0ec7d8a49bc88.png)

Not related but I did come across this adding Python mode in 4.1.1:

> <https://github.com/processing/processing4/issues/613>
>
> \## Description
> In Processing 4.1.1 it is currently seemingly impossible to down…load and switch between modes.
> 
> \## Expected Behavior
> In Processing 3.5.4 if you open the "Modes" tab in the "Contribution Manager" window, there is a list of modes you can potentially install. At the very least you should find "R Mode" and "Python Mode". You can download any of these (the ones that are supported anyways) and than can use them in Processing.
> 
> \## Current Behavior
> In Processing 4.1.1 (and 4.1 and possibly earlier versions I haven't tested) when you click "Manage Modes..." you are taken to an empty "Modes" tab in the "Contribution Manager" window. There are no modes ready to download, therefore you are stuck in Java mode.
> 
> \## Steps to Reproduce
> 1. Run Processing 4.1.\*
> 2. Click on the selector with the word "Java" and a little downward triangle in it
> 3. Click on "Manage Modes..."
> 
> \## Your Environment
> \* Processing version: 4.1.1
> \* Operating System and OS version: Windows 11 Pro x64 22H2 Build: 22621.900
> 
> \## Possible Causes / Solutions
> Not sure about the cause but I found a workaround (though haven't tested fully).
> I downloaded Processing 3.5.4 and installed Python mode on it.
> I than opened Processing 4.1.1 and I found that it also had Python mode installed.
> The Modes tab was still empty, but apparently the mode for 3.5.4 was saved in the same place 4.1.1 was looking, and it at least thinks it can be used. I'm not sure how well it works.
> 
> Image:
> !\[image\](https://user-images.githubusercontent.com/6439157/204891586-96bee15a-c6b1-41ae-a295-c66902c92a62.png)

`:)`