GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Display detection fails in Processing 4.5.6 on macOS + pixelDensity() · Issue #1551 · processing/processing4

Display detection fails in Processing 4.5.6 on macOS + pixelDensity() #1551

New issue
Copy link
New issue
Copy link
Closed
Closed
Display detection fails in Processing 4.5.6 on macOS + pixelDensity()#1551
Copy link
Assignees
manoellribeiro
Labels
bugSomething isn't workingSomething isn't working

Description

@SableRaf
SableRaf
opened on Jul 20, 2026
Issue body actions

Most appropriate sub-area of Processing 4?

Core/Environment/Rendering

Processing version

4.5.6

Operating system

macOS Tahoe 26.5.2 (25F84)

Bug description

Running an empty sketch in Processing 4.5.6 produces the following warnings:

display count needs to be implemented for non-AWT
AWT disabled, displayWidth/displayHeight will be 0

Additionally, calling pixelDensity(2) produces this error:

pixelDensity(2) is not available for this display

Processing should detect the display dimensions and use pixelDensity(2) by default on the built-in Retina display.

Regression for:

  • Add warning for default pixelDensity behavior #1226
  • Change the default display density #1038

Steps to reproduce this

  1. Install Processing 4.5.6 on macOS.
  2. Open Processing and create a new sketch.
  3. Run the sketch below.
  4. Observe the display-count and displayWidth/displayHeight warnings in the console.
  5. Uncomment pixelDensity(2).
  6. Run the sketch again.
  7. Observe the pixelDensity(2) is not available for this display error.

snippet

void setup(){
  size(640,400);
  //pixelDensity(2);
}

void draw(){
  line(10,10,630,390);
}

Additional context

Image

Would you like to work on the issue?

No, I’m just reporting the issue

Activity

  1. SableRaf
    assigned
    catilac
    on Jul 20, 2026
  2. SableRaf
    added
    bugSomething isn't workingSomething isn't working
    on Jul 20, 2026
  3. SableRaf commented on Aug 31, 2026

    @SableRaf
    SableRaf
    on Aug 31, 2026
    CollaboratorAuthor
    More actions

    Note: a related discussion is happening here on the forum: https://discourse.processing.org/t/display-count-needs-to-be-implemented-for-non-awt/49232

  4. AlexRussellArtist commented on Aug 31, 2026

    @AlexRussellArtist
    AlexRussellArtist
    on Aug 31, 2026
    More actions

    The discussion @SableRaf mentions relates to the same
    "display count needs to be implemented for non-AWT AWT disabled, displayWidth/displayHeight will be 0"
    error message, but on Windows 11. Running his snippet does not throw the
    "pixelDensity(2) is not available for this display"
    on (my) PC.

  5. SableRaf commented on Sep 11, 2026

    @SableRaf
    SableRaf
    on Sep 11, 2026
    CollaboratorAuthor
    More actions

    cc @manoellribeiro

  6. manoellribeiro commented on Sep 11, 2026

    @manoellribeiro
    manoellribeiro
    on Sep 11, 2026
    More actions

    thanks @SableRaf , reading about it

  7. SableRaf
    assigned
    manoellribeiro
    and unassigned
    catilac
    on Sep 12, 2026
  8. SableRaf commented on Sep 12, 2026

    @SableRaf
    SableRaf
    on Sep 12, 2026
    CollaboratorAuthor
    More actions

    Sure thing @manoellribeiro! I re-assigned it to you. Thanks for looking into it.

  9. tychedelia
    added a commit that references this issue on Sep 14, 2026

    Fix: only pass --disable-awt for WebGPU renderer

    76feca7
  10. catilac commented on Sep 18, 2026

    @catilac
    catilac
    on Sep 18, 2026
    Collaborator
    More actions

    this is fixed in 4.5.7!

    Reacted by Leo
    Reacted by Ülgen Sarıkavak and Manoel Ribeiro
  11. catilac
    closed this as completedon Sep 18, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

  • @manoellribeiro
    manoellribeiro

Labels

bugSomething isn't workingSomething isn't working

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

    You are visitor 01402503 — GeezerVison does not store the pages you look up.
    Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.