Extapp web simulator not refresh the screen

[Valmontechno]

Describe the bug

In some cases, the external application web simulator does not refresh the screen, whereas a real calculator displays correctly.

To Reproduce

Here, the simulator displays B without displaying A.

#include "eadkpp.h"

const char eadk_app_name[]
#if PLATFORM_DEVICE
    __attribute__((section(".rodata.eadk_app_name")))
#endif
    = "Num Wild";

const uint32_t eadk_api_level
#if PLATFORM_DEVICE
    __attribute__((section(".rodata.eadk_api_level")))
#endif
    = 0;

using namespace EADK;

int main()
{
    Keyboard::State keyState;

    Display::pushRectUniform(Screen::Rect, 0xf6f6f6);
    Display::drawString("A", Point(0, 0), true, 0x414041, 0xf6f6f6);
    Timing::msleep(1000);
    Display::drawString("B", Point(0, 0), true, 0x414041, 0xf6f6f6);

    while (true)
    {
        keyState = Keyboard::scan();
    }
}

If keyState = Keyboard::scan(); is deleted, nothing will be displayed.

This extract still displays nothing.

while (true) {
    Display::drawString("A", Point(0, 0), true, 0x414041, 0xf6f6f6);
    Display::drawString("B", Point(0, 0), true, 0x414041, 0xf6f6f6);
}

Expected behavior

We expect the save behavior that a real calculator.
The first example must be display A then B after 1 second. The second must be blink A and B.

Environment

• Epsilon version: 24.10.0
• Platform: Web simulator
• Browsers: Google Chrome, Microsoft Edge, Mozilla Firefox

[MateoNumworks]

Hi,
On simulator, screen refreshing is only done when scaning the keyboard, see line 117:

epsilon/ion/src/simulator/shared/keyboard.cpp

Lines 103 to 118 in a80246d

	State scan(bool forPython) {
	State state(0);
	if (Simulator::Window::isHeadless()) {
	return state;
	}
	// We need to tell SDL to get new state from the host OS
	SDL_PumpEvents();
	// Notify callbacks in case we need to do something
	Simulator::Keyboard::didScan();
	// Grab this opportunity to refresh the display if needed
	Simulator::Window::refresh();

This is intended as the calculator (and thus simulator) does not require screen refreshes without any event happening

To solve this issue, you need to manually call Keyboard::scan() when you want a new frame on your simulator.

[yannis300307]

Note that calling keyboard::scan() each time you draw a rect or a pixel to the screen is very slow. I tried to call keyboard::scan() each time I draw something to the screen to simulate the non-buffered screen of the calculator in my Rust template and it made the simulator extremely slow (Much slower than the actual calculator). So you should avoid doing this.