processing / processing/processing4
Need non-AWT ways to get display count, width, height, pixel density
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 497
- Forks
- 183
- Avg merge
- 4h 39m
- Merged PRs (30d)
- 3
Description
Created by: benfry
We need either 1) an alternative/native method to make these work, or 2) a per-Surface version of them.
The second option is still problematic since we don't know what PSurface will be used when settings() is called. So either we need to start passing that to the command line, or do something more clever, i.e. once size() or fullScreen() is called, use the renderer to create an object that can handle these device settings on a per-surface type basis.
For now, displayWidth and displayHeight will be 0 when --disable-awt is used.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how displayWidth, displayHeight, and pixel density are handled when --disable-awt is used, then examine the size(), fullScreen(), renderer, and PSurface paths mentioned in the issue. Done means providing a defined non-AWT implementation or a workable per-Surface approach instead of returning 0 for display dimensions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100