ESD RAM_DL vs. RAM_G usage

[ndsmith34]

I am developing a project on ESD 4.8 and when I upload the code to the hardware the screen update rate is very sluggish and the response to user input is very delayed. I also notice that my RAM_DL usage (as reported by ESD) is nearly 100%, while RAM_G usage is very low (around 1k). Are these things related? Is there a way in ESD to shift how the memory is used?

[ndsmith34]

So I was able to figure out that the sluggishness of the display was not a RAM issue and was able to correct it.
However, as I'm using a Scroll Switch Page as the main layout for my application. As I add more User Pages to the page containing the Scroll Switch Page layout, the RAM_DL fills up. Eventually when I add enough pages the preview will no longer render and I get a recurring warning saying "Coprocessor has flagged an error."
Is there anything I can do to correct this? Am I limited on the number of pages I can have in a Scroll Switch Page?

[BRT Community]

Hi,

Yes you will get an error if you run out of RAM_DL.

RAM_G is the general purpose RAM which can be used to store assets such as fonts and images, whereas the RAM_DL is the area which is parsed by the graphics engine when it renders the screen.

In EVE in general, you can sometimes trade off RAM_G with RAM_DL, for example by changing a logo from a text string and shapes to being a bitmap image (as the bitmap goes in RAM_G whereas the text and shapes would be in RAM_DL). However, in ESD it is more difficult to optimise the content as most content is composed of widgets. If you do have any logos etc. you could consider making them into an image instead.

What settings do you use in your Scroll Switch Page?

Best Regards, BRT Community