-
Notifications
You must be signed in to change notification settings - Fork 101
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
How to put and create custom logos into the firmware? #320
Comments
Yes, it is.
Am 24.04.2017 07:51 schrieb "the27club" <notifications@github.com>:
I am just wanting to create a logo to add on to my RX200s, but still want
to keep the firmware.
Is this possible?
please excuse my ignorance if there is..
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#320>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AWiTjs2MNPpI6_pTIGr-OXgxrU7WRJLgks5rzDh2gaJpZM4NFuPL>
.
|
Yeah. How do you do it though? |
Use a graphics program with which you can create 1-bit images.
Then create your picture in the appropriate resolution (64 x 40 px, 96 dot)
and save it as .bmp file.
Take the FwUpdater from Wismec and select LOGO button, now select your
created logo and it will be added.
|
so I did this and it doesn't cover the clock. I see the logo but the bottom part of the clock still shows. Logo can't be over 64x48 |
This is true, the logo can not go over the entire screen resolution. The
Wismec RX 200S has max. 64 x 48 px for the logo. In the menu under Screen
at Logo, select Where on "Top"
|
Post a picture please. |
Try my fork, I step on this shit and fix week ago. |
I buy mine here.... 1 Buck each logo. And they are really good and handmade! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I am just wanting to create a logo to add on to my RX200s, but still want to keep the firmware.
Is this possible?
please excuse my ignorance if there is..
The text was updated successfully, but these errors were encountered: