processing / processing/processing4
`fullScreen(P2D, SPAN)` does not span across multiple displays on macOS
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 494
- Forks
- 183
- Avg merge
- 4h 39m
- Merged PRs (30d)
- 3
Description
Most appropriate sub-area of Processing 4?
Core/Environment/Rendering
Processing version
4.5.2
Operating system
MacOS 15.6.1 (24G90)
Bug description
The reference for fullScreen() states that using SPAN should run the sketch “at the full dimensions across all of the attached screens”.
When running a sketch with fullScreen(P2D, SPAN) on my setup, the sketch only appears on the main display.
Hardware setup: 3 external displays connected through an iVANKY FusionDock Max 1 (Note: this is not using DisplayLink):
- DisplayPort → Dell U2720Q (3840×2160)
- HDMI → Dell U2419H (1920×1080)
- HDMI → Dell U2419H (1920×1080)
Steps to reproduce this
- Connect multiple displays to a macOS machine.
- Run the sketch below in Processing 4.5.2 (macOS)
- Observe whether the rendered output spans continuously across all displays.
snippet
// If more than one screen is attached to the computer, run the
// code at the full dimensions across all of the attached screens
int x = 0;
void setup() {
fullScreen(P2D, SPAN);
background(0);
noStroke();
fill(102);
}
void draw() {
rect(x, height*0.2, 1, height*0.6);
x = x + 2;
}
Additional context
This may be related to #1426
Would you like to work on the issue?
No, I’m just reporting the issue
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 running the provided Processing sketch with multiple displays on macOS and compare the behavior with the fullScreen() reference. Review the related issue #1426 for context; done means P2D with SPAN renders continuously across all attached displays rather than only the main display.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- computer-graphics, desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100