Skip to content

Add customizable boot logo based on resolution #7146

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

Merged
merged 1 commit into from
Jul 2, 2025

Conversation

vidplace7
Copy link
Member

@vidplace7 vidplace7 commented Jun 26, 2025

Adds customizable boot logos based upon device screen resolution.

Builds upon:

This platformio script callback determines the display resolution, locates the corresponding branding/logo_<width>x<height>.png and loads it onto data/boot/logo.png.

See the logo_xxx.png files in event/defcon33 branding for our first example.

DefCon here we come ☠️

@vidplace7
Copy link
Member Author

vidplace7 commented Jun 26, 2025

DRAFT until I figure out what to do about devices with physically-rotated displays (T-Deck)

@vidplace7 vidplace7 requested a review from mverch67 June 27, 2025 00:06
@vidplace7 vidplace7 force-pushed the load_branding branch 2 times, most recently from ee56cf8 to abb8b88 Compare June 27, 2025 01:32
@vidplace7 vidplace7 force-pushed the load_branding branch 3 times, most recently from aac9457 to 2819251 Compare June 27, 2025 12:56
@vidplace7 vidplace7 marked this pull request as ready for review June 27, 2025 12:56
@vidplace7 vidplace7 force-pushed the load_branding branch 2 times, most recently from 349cfab to cb4eede Compare June 29, 2025 13:09
Copy link
Collaborator

@mverch67 mverch67 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As discussed I think we definitely should not use the SCREEN_ROTATE macro for this. Besides that it's now really ugly to have it moved from variant.h into platformio.ini (which nobody will understand why and which is kinda error prone) this macro is not used by MUI but now should be used together with two other macros to determine the boot logo size.... eek.
I'd rather suggest to use an either explicit (e.g. USE_BOOTLOGO=logo_320x480.png) or implicit (e.g. DISPLAY_SIZE=320x480) macro that helps to handle the size and orientation of the boot logo.

@vidplace7 vidplace7 force-pushed the load_branding branch 5 times, most recently from ea6efab to bff9013 Compare July 1, 2025 16:38
@vidplace7 vidplace7 requested a review from mverch67 July 1, 2025 16:38
@vidplace7 vidplace7 force-pushed the load_branding branch 2 times, most recently from ff3bb9f to 5ef04ef Compare July 1, 2025 17:06
@vidplace7 vidplace7 requested a review from mverch67 July 1, 2025 17:09
@vidplace7 vidplace7 marked this pull request as draft July 1, 2025 18:19
@vidplace7 vidplace7 marked this pull request as ready for review July 1, 2025 18:32
@vidplace7 vidplace7 force-pushed the load_branding branch 2 times, most recently from eda2138 to 34f3a4f Compare July 2, 2025 13:06
@rcarteraz rcarteraz merged commit f99ac21 into meshtastic:master Jul 2, 2025
52 checks passed
@vidplace7 vidplace7 deleted the load_branding branch July 2, 2025 23:27
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.

3 participants