Skip to content

Update how board.DISPLAY is checked #96

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from
Closed

Update how board.DISPLAY is checked #96

wants to merge 1 commit into from

Conversation

jepler
Copy link
Contributor

@jepler jepler commented Feb 12, 2025

Historically, boards with no built-in display have not had a board.DISPLAY property.

Soon, with adafruit/circuitpython#10028, any board with displayio will have a board.DISPLAY property. This property will be None if no display is configured, or a truthy non-None value if a display is configured (including dynamically at runtime).

This revised check will work on both old and new circuitpython versions.

Historically, boards with no built-in display have not had a `board.DISPLAY` property.

Soon, with adafruit/circuitpython#10028, any board with displayio will have a `board.DISPLAY` property. This property will be `None` if no display is configured, or a truthy non-`None` value if a display is configured (including dynamically at runtime).

This revised check will work on both old and new circuitpython versions.
Copy link

👋 Thanks for this pull request! Unfortunately, it looks like the automated continuous integration (CI) test(s) failed. These can be tricky to fix so we've written a guide on how to fix them locally. It has pages about running pre-commit locally and another about building the docs locally with sphinx. Thanks for contributing to CircuitPython! If you have more questions, feel free to join the Adafruit Discord and post in #circuitpython-dev.

@jepler
Copy link
Contributor Author

jepler commented Feb 15, 2025

Over in circuitpython we ended up going with supervisor.runtime.display instead of board.DISPLAY for the new functionality. As such, this PR is not useful to merge after all.

@jepler jepler closed this Feb 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant