Open w4tsn opened 3 weeks ago
Build checks have not completed. Possible reasons for this are:
I'm more of a TNG fan :wink: but this looks nice :+1:
Having the background as an image really is using a lot of storage space. Alas, you can not render images from the SPI flash, so making this fit is going to be difficult. Have you been able to run it on the device, not the simulator?
If you decide to convert it to be rendered "vector graphics style" with lvgl, watch out for the heap memory usage. If you go crazy detailed (like I did once with my watch face), you can easily fill the heap completely and get weird behaviour that does not show on the sim.
For an immediate size decrease of the background picture, you could also use one of lvgl's indexed color modes. If you convert to 4 or 8 bit indexed color, you can only have 16 or 265 colors, respectively (16 will certainly make your curves look less anti-aliased), but the storage use would decrease to 29kB or 58kB.
You alignment issue is a funny one that definitely never happened to anyone I know :wink:.
You pass the value -5
to an argument of type uint8_t
.
Edit: Marked wrong statement
I'm more of a TNG fan 😉 but this looks nice 👍
Thanks! Your TNG Version is also pretty cool, but as you can guess I'm more of a Voyager fan :D
Having the background as an image really is using a lot of storage space. Alas, you can not render images from the SPI flash, so making this fit is going to be difficult. Have you been able to run it on the device, not the simulator? If you decide to convert it to be rendered "vector graphics style" with lvgl, watch out for the heap memory usage. If you go crazy detailed (like I did once with my watch face), you can easily fill the heap completely and get weird behaviour that does not show on the sim. For an immediate size decrease of the background picture, you could also use one of lvgl's indexed color modes. If you convert to 4 or 8 bit indexed color, you can only have 16 or 265 colors, respectively (16 will certainly make your curves look less anti-aliased), but the storage use would decrease to 29kB or 58kB.
Thanks, I'll look into that!
You alignment issue is a funny one that definitely never happened to anyone I know 😉. You pass the value
-5
to an argument of typeuint8_t
.
Oh my....
Alas, you can not render images from the SPI flash
This is wrong. I got mixed up while thinking about how I went to optimize the storage needs of my development. I tried to save space by re-using duplicate parts, but I could not get the rotation features of lvgl to work. It turned out it is not possible to rotate images that are displayed from the SPI flash.
You clearly can render images from SPI flash (actually you do it). But I would also think this is the reason the watch face loads slowly. Nevertheless indexed color will probably speed things up by giving you size reduction.
@w4tsn I really like this watchface. Do you think it is possible to additionally add the current weather information? Probably the most useful way would be to make it configurable. E.g. I don't use the heart rate measurement because it drains the battery so fast but I like to know the (rough) temperature. An option to configure the available information like in the PineTimeStyle watchface were awesome but I understand if this takes some time since it increases the complexity of the watch face considerably.
This adds an LCARS watchface, a UI known from the Star Trek series.
The following issues are still open and I might need a hand with these:
Screencast from 2024-06-03 18-34-02.webm
EDIT: here the pre-build OTA files for the firmware and resources.
pinetime-mcuboot-app-dfu-1.14.0.zip infinitime-resources-1.14.0.zip