Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pixelDensity() not working in Windows applications #487

Closed
processing-bot opened this issue May 18, 2022 · 3 comments
Closed

pixelDensity() not working in Windows applications #487

processing-bot opened this issue May 18, 2022 · 3 comments

Comments

@processing-bot
Copy link
Collaborator

Created by: dgray001

seems very similar to processing/processing#5414

Description

Scales to window scaling (default 125%).
When I run displayDensity() it returns 1
If I run pixelDensity(1) or pixelDensity(displayDensity()) I get the error:
Display -1 does not exist, returning 1 for displayDensity(-1)

Expected Behavior

Sketch to scale with Windows scale

Current Behavior

Sketch scales to 125% to what it should be

Steps to Reproduce

  1. Set Windows scale to anything not 100%
  2. Use processing 4

Your Environment

  • Processing version: 4.0b8 (also tried 4.0b6 with same behavior)
  • Operating System and OS version: Windows 11
  • Other information: Brand new workstation with clean install of windows/processing
  • EDIT: I'm using javafx not sure if that makes a difference

Possible Causes / Solutions

This only happens in processing4; when I run on processing3 there is no issue.

@processing-bot
Copy link
Collaborator Author

Created by: benfry

Just ran into something similar while trying this with fullScreen() on macOS, but with any luck, it should fix the issue for Windows as well. The fix will be in 4.0.2 when released.

@processing-bot
Copy link
Collaborator Author

Created by: benfry

Meant to tag this from this commit: b0cd253

@processing-bot
Copy link
Collaborator Author

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 17, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant