We are facing a critical issue with the alphabetical ordering of bitmap identifiers in the BitmapDatabase.hpp file automatically generated by TouchGFX Designer 4.25.
When comparing two consecutive commits in our project, we identified that rendering problems began to occur after a UI design update. After detailed analysis, we discovered an inconsistency in the ordering of bitmap identifiers that appears to be causing these issues.
I noted this issues when using a animation widget with variable BITMAP_FRAME_00_DELAY_0_07S_ID to BITMAP_FRAME_78_DELAY_0_07S_ID. After a refactorer images, I chaged another files with the same initial name "FRAME_xx".
Specific Example:
In the generated file, identifiers for frames with different dimensions are interspersed between sequentially numbered frames, resulting in an ordering like this:
const uint16_t BITMAP_FRAME_11_DELAY_0_03S_ID = 71;
const uint16_t BITMAP_FRAME_120X234_ID = 72; // Dimensioned frame interspersed
const uint16_t BITMAP_FRAME_12_DELAY_0_07S_ID = 73;
// ... more numbered frames ...
const uint16_t BITMAP_FRAME_17_DELAY_0_03S_ID = 78;
const uint16_t BITMAP_FRAME_180X234_ID = 79; // Another dimensioned frame interspersed
const uint16_t BITMAP_FRAME_18_DELAY_0_07S_ID = 80;
const uint16_t BITMAP_FRAME_190X110_ID = 81; // Yet another dimensioned frame
// And so on...
The correct alphabetical ordering should group all numbered frames together and then all dimensioned frames, maintaining a logical sequence:
// First all numbered frames
const uint16_t BITMAP_FRAME_00_DELAY_0_07S_ID = 60;
// ... up to ...
const uint16_t BITMAP_FRAME_32_DELAY_0_07S_ID = 92;
// Then all dimensioned frames
const uint16_t BITMAP_FRAME_120X234_ID = 93;
const uint16_t BITMAP_FRAME_180X234_ID = 94;
// ... and so on ...
Impact: This incorrect ordering appears to be affecting the rendering of components on screen, causing undesired visual effects and possibly timing issues in animations.
- The issue occurs when making significant layout changes using TouchGFX Designer
- New components are added that reference new bitmaps
- The generated BitmapDatabase.hpp has inconsistent alphabetical ordering
Questions:
- The example I gave of how the files were ordered by Touchgfx, is it correct or should it be the other way I gave?
- Is there any configuration to fix this ordering, or is it necessary to manually edit the file after each generation?
Soluction: in this case was simple, I just rename the files and fix it, but cost me a lot to understand the issues source.
Thanks!
