Processing 4 displayDensity() on a 4k display result is incorrect

[processing-bot]

Created by: markcosmic

Description

Expected Behavior

in using displayDensity() on my 4K display, I was expecting the results to be the same as when I use it in Processing 3

Current Behavior

in using displayDensity() on my 4K display, the result is "1"

Steps to Reproduce

1. println(displayDensity());

Your Environment

• Processing version: Processing 4
• Operating System and OS version: window 10 pro 21h1
• Other information: Using an Asus ZenBook UX581GV.308

Possible Causes / Solutions

[processing-bot]

In GitLab by @mrbbp on Jan 19, 2022, 17:40

Does it suppose to print 2?
what is your width in fullscreen()?

[processing-bot]

Created by: markcosmic

my screen width is 3840.
in processing 3 I get a 2 result
in processing 4 I get a 1 result

[processing-bot]

Created by: benfry

Ok, confirmed… Was thinking something has just changed in Java 17 on Windows, but when using Export to Application, displayDensity() is returning 2 again. (So I'm looking into it further.)

On the plus side, even when this happens, you're getting the full resolution—it's just that it's not doing the automatic 2x handling for you.

[processing-bot]

Created by: benfry

Ok, found and fixed. The workaround for older setups was still in place. 4.0 beta 4 will have the fix.

[processing-bot]

Created by: github-actions[bot]

This issue has been automatically locked. To avoid confusion with reports that have already been resolved, closed issues are automatically locked 30 days after the last comment. Please open a new issue for related bugs.