Hi,
There are a couple of things that may help with regards to your questions although there may also be other ways using EVE's GPU and widget features to achieve it without swapping bitmaps as this can risk tearing etc.
For the display list itself, EVE has double buffering and so if you create your content using graphic primitives and widgets then it will be double buffered. It also avoids the need to manually create and edit bitmaps unless the application needs this in particular (for example a line can be drawn by specifying the start and end point and EVE will work out how to draw the line). You can also optimise it to avoid completely re-sending the list - for example, you can use the append command to append a list of static items which you have created and then add some dynamic numbers or text for readouts. What was your overall requirement for the application?
For your question about images and changing during the scan-out,
EVE has bitmap formats such as RGB332 and ARGB2 (if you need alpha) which use 1 byte per pixel and so could fit two images in RAM_G.
The BT81x has a command CMD_SYNC which allows you to wait for the end of the scan out and so can help avoid tearing. You can use this to help when editing the data on the fly of a bitmap for example or updating a macro value as shown here.
//To update REG_MACRO_0 at the end of scan out, to avoid tearing:
cmd_sync();
cmd_memwrite(REG_MACRO_0, 4);
cmd(value);
Best Regards, BRT Community