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
- jeremydouglass September 2016
- kfrajer September 2016
- O_Yilmazer September 2016
High DPI displays / Microsoft Surface
When opening Processing (3.0, 3.0.1, 3.0.2) on a Microsoft Surface the program is displayed in a very small scaled window. This problem is not present in other Windows 10 installations I have. It appears to be unique to the high resolution of the display. I have confirmed that the system wide display scaling does not scale this up as it should when running different compatibility modes. The initial banner will actually be scaled, but the internal fonts of the menu, line numbering, and console are not increased. Increasing the two font values in the editor preferences does not help either. Any thoughts? Essentially I think I'm running into issues with a high res or 'retina' port of the application. This may be a Java dependency though.
Answers
Hi,
Is there an know fix?
O_Yilmazer, if there isn't an issue already posted on https://github.com/processing/processing/issues then I encourage you to report this -- reporting it is the only way it will get fixed!
A quick search show me the problem exist from a while with no solution so far:
https://github.com/processing/processing/issues/2411
I hope the address the issue soon.
Kf