processing / processing/processing4

full screen bug with few device

Offen
#1,524 1 Kommentar 1 Reaktion 1 zugewiesene Person Auf GitHub ansehen

@catilac arbeitet bereits daran.

Seit 09.6.2026.

bug
Vorherrschende Sprache
Java
Sterne
494
Forks
183
Ø Merge
4 Std. 39 Min.
Gemergte PRs (30 T.)
3

Beschreibung

Most appropriate sub-area of Processing 4?

Core/Environment/Rendering

Processing version

Processing 4.5.2

Operating system

MacOS Tahoe 26.4.2

Bug description

With my Video Projector BenQ PJ in fullscreen() in P3Dand in P2D the window is place on the main screen.
In classic mode that's ok.

Image

May be it's due from my VP because this one is old, I don't know. The definition of my VP is 1920x1080
To fix it I use this code :

import java.awt.GraphicsEnvironment;
import java.awt.GraphicsDevice;
import java.awt.Rectangle;

int target_screen = 2;
void setup() {
  fullScreen(P3D,target_screen);
  secure_screen_place(target_screen);
}

void secure_screen_place(int target) {
  GraphicsEnvironment environment = GraphicsEnvironment.getLocalGraphicsEnvironment();
  GraphicsDevice[] devices = environment.getScreenDevices();
  Rectangle rect = devices[this.display -1].getDefaultConfiguration().getBounds();
  surface.setLocation(0,0);
  int x = (int)rect.getX();
  int y = (int)rect.getY();
  println("repositionnement", x, y);
  surface.setLocation(x,y);
}

For an unknown reason it's necessary to set in first the location to zero before move to goal position.

May be it's linked to
https://github.com/processing/processing4/issues/1518
https://github.com/processing/processing4/issues/1426

I fix this bug in Processing If you're interested I can push it !!!
But it's more an hack, because It's hard to manage the variable between the static and the non static class PApplet and PSurface

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
  3. Forke das Repository und arbeite in einem Branch.
  4. Öffne einen Pull Request, der die Issue-Nummer nennt.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.