Hi, I’m new here. When I first started looking into new firmware for the Cocoon Create Touch I soon realised that its nearly impossible for a lay person to create the LCD image without the .bmp files from the source code. I am curious as to why the .bmp files for the screen are not included in the Github source? I’m not having a go at you, im just curious.
The repository on GitHub contains everything necessary. If it like if you said: “it is nearly impossible for a lay person to create executables from the source code”. Source code contains… source code. BMP files are artifacts generated from the source code, so they have nothing to do in a source repository.
Also, please post next time in the appropriate category, as explained in the rules of this Community. I will move your topic to Get Help (where question about ADVi3++ should be).
Without the .bmp there is no functional GUI for the 3D printer. When you open the .hmi file in DGUS from the source the .tft files are linked to .bmp’s but in GitHub these are not there.
My apologies for not posting in the appropriate category
BMP files are generated from the Sketch file.
More precisely: PNG images are generated from the Sketch file (for screens but also for widgets). Then they are converted into BMP3 format (bottom-up images, not regular ones). The scrips I am using to automate that are under
Scripts in the GitHub repository. They are however tailored for the environment I am using (i.e. macOS and Sketch app).