processing / processing/processing4

full screen bug with few device

Abierto
#1,524 1 comentario 1 reacción 1 asignado Ver en GitHub

@catilac ya está trabajando en esto.

Desde el 9/6/2026.

bug
Lenguaje dominante
Java
Estrellas
494
Forks
183
Merge medio
4 h 39 min
PR fusionados (30 d)
3

Descripción

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

Guía de contribución

Abrir la guía de contribución

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.