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
Management of size() on Retina displays
First, let me say I'm new to Processing, but an accomplished programmer and was recently looking for something for quick algorithm prototyping, and have found Processing a perfect match for what I was looking for.
My question relates to size(), pixelDensity() and displayDensity() ... I believe I understand them correctly, the only thing that tripped me up was the need to use pixelWidth and pixelHeight when doing pixel based operations. But it would seem to me that if I'm creating something for a "normal" display, to be projected say, then I might use something like size(1920,1080). But on a retina display like my MacBookPro I would normally use something smaller, but knowing that the quality will be the same as higher in that smaller window.
In short it doesn't seem that I can make decisions on the values for size() based upon displayDensity()? It would seem like a natural thing to want to do if developing for both retina and non-retina. Or more fundamental, I would like to be able to base the values for size() on the display pixel dimensions. Any way to do this?