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
P5JS createGraphics scaling discrepancy?
I'm seeing a scaling discrepancy between the default graphics context and a second context of the same size created with the "createGraphics()" function. I have a demonstration of the bug(?) up on OpenProcessing: createGraphics
Might be an issue with my hardware since I'm using a surface pro 4 which has a high density display. If that's the case, is there a way to fix it? Thought it might be "devicePixelScaling()", but that's not available in p5js. Are people with regular density displays seeing the same behavior, or does it seem to work fine for you?
Thanks,
Albert
Answers
Found a computer with ordinary density display and the discrepancy is not there, so it's definitely related to the high density display on the surface pro 4. Is there a fix for this so that I don't have to worry about what kind of display the user might be using?
http://p5js.org/reference/#/p5/pixelDensity
http://p5js.org/reference/#/p5/displayDensity
I found these, but they don't seem to fix the problem. Maybe I'm using them incorrectly. I'll keep experimenting and let the thread know if I resolve it. Thanks.
I don't have the so-called "retina" display hardware, so I can't do tests by myself. 8-|
But have you tried to call pixelDensity() over your p5.Graphics object? >-)
So, still testing, and about to be afk for a while, but I called displayDensity on the default graphics context and the second one that I created using createGraphics(). Both report "2", whatever that means. Just for the hell of it, I set the pixelDensity of the second graphics context (the one created with createGraphics) to "1" and left the other one alone, and that makes the coordinate systems line up.
I don't know why these numbers are what they are, or why setting the pixelDensity to "1" on the second graphics context resolves the issue. I also am not sure what this will do on a normal density display. More to come... Thanks again.
If displayDensity() returns
1, it means we don't have any sorta hi-res display AFAIK. L-)Good news. Setting pixelDensity to "1" on the second graphics context seems to work fine on both hi-res and ordinary displays.