What are point() and line() doing on the pixel level?

mscottveach

Looking at the result of point and line under a magnifying glass, I realized that my assumption that there was a 1 to 1 correspondence between processing pixels and my monitor's pixels was naive.

I was surprised by a few things:

When I try to draw a line using a series of point calls, it looks very different than when I use line and neither one always does what I expected. (For example, drawing a simple line segment will look one way in isolation and then the entire line will look different if its drawn so that one of it's ends is adjacent to a different line.)

Can anyone point me to a source where I can learn what's happening on the pixel level with these functions.

GoToLoop

1. https://Processing.org/reference/line_.html
2. https://Processing.org/reference/strokeWeight_.html
3. https://Processing.org/reference/strokeCap_.html
4. https://Processing.org/reference/strokeJoin_.html
5. https://Processing.org/reference/smooth_.html
6. https://Processing.org/reference/noSmooth_.html

mscottveach

Thanks for the reply. Most of the weirdness I was seeing turned out to be the result of my call to NoSmooth() being in the wrong place. So I thought anti-aliasing was off but it was actually on - and I think that's why I was getting weird results on the pixel level.

My other big question was whether line was pixel inclusive on both ends. The reference doesn't specify but with anti-aliasing off I was able to see with a magnifying glass.