Touch gfx code optimization

[jijomathew]

hello, 

I'm currently developing an application that features more than 150 screens. However, I've encountered a significant challenge: once I build the code, the overall size exceeds the available flash memory. While I'm using external flash for images, I still need a solution to accommodate the large code base . What strategies or best practices can I implement to optimize my application’s size and ensure it runs smoothly? Any insights or recommendations would be greatly appreciated!

[GaetanGodart]

Hello @jijomathew ,

Could you maybe "merge" multiple screens into one.
For instance, if you have 2 screens that are quite similar, one to setup the hours and one to setup the minutes, instead of making 2 screens, just make one and just change a text area at the top to know if you are setting the hours or the minutes.
150 screens is quite a lot.

Also, is your compiler optimized for size?

Regards,

[jijomathew]

Hello,

I am using External quad SPI Flash to store images and other touch GFX Assets, Rather than Placing entire Application code in to  Quad SPI ,Can I place Certain Part of My code Like Certain Functions inside quad SPI by utilizing the XIP(Execute in Place) feature of quad SPI flash in Memory mapped Mode.

Thanks and Regards

JIJO