Howdy, Stranger!
We are about to switch to a new forum software. Until then we have removed the registration on this forum.
Categories
- All Categories 25.7K
- Announcements & Guidelines 13
- Common Questions 30
- Using Processing 22.1K
- Programming Questions 12.2K
- Questions about Code 6.4K
- How To... 4.2K
- Hello Processing 72
- GLSL / Shaders 292
- Library Questions 4K
- Hardware, Integration & Other Languages 2.7K
- Kinect 668
- Arduino 1K
- Raspberry PI 188
- Questions about Modes 2K
- Android Mode 1.3K
- JavaScript Mode 413
- Python Mode 205
- Questions about Tools 100
- Espanol 5
- Developing Processing 548
- Create & Announce Libraries 211
- Create & Announce Modes 19
- Create & Announce Tools 29
- Summer of Code 2018 93
- Rails Girls Summer of Code 2017 3
- Summer of Code 2017 49
- Summer of Code 2016 4
- Summer of Code 2015 40
- Summer of Code 2014 22
- p5.js 1.6K
- p5.js Programming Questions 947
- p5.js Library Questions 315
- p5.js Development Questions 31
- General 1.4K
- Events & Opportunities 288
- General Discussion 365
In this Discussion
- jschifano December 2016
- laimperiestro December 2016
Why does using pixelDensity(2) output "2 1" to the console every time I run a sketch?
When I use pixelDensity in a sketch, it outputs the following to the console when the sketch runs:
"2 1". I don't have any print or println in my sketch, so confused why it does this.
See attached screenshot.
Is this just me or does everyone experience this?
Tagged:
Answers
Hello @jschifano
pixelDensity means pixels per inch, so if you write
Hi, this is great, but I guess what I'm saying is "why" does it feel the need to write this info to the console? It doesn't seem like may other processing methods write output to the console unless you use print or println. Seems kinda random, no?
Hello
I really not sure why only a few processing methods write some information to the console, I guess some libraries include it, but because the author considers useful....
Ah got it. Thanks for the lowdown @laimperiestro! :-*