Generally it will be running tight loops where it waits for the co processor to finish. It'll be easiest to just put a 1ms sleep in those loops. You may also put the 1ms wait in the "Idle" function of your app instead, since that gets called during tight loops (Create an Idle slot under App.main, double click to go to user code, and put in the sleep code).

The main loop builds a new display list for each frame, which is necessary for animating widgets. Ideally the render portion of the loop will be called at the same rate as the frame rate.

An alternative could be to do a blocking wait on the main thread, instead of spinning the thread, and make use of the interrupt output pin of the EVE chip to resume the thread, but that may involve some platform specific code.

You can manually create an Eclipse project under a subdirectory of the ESD project, and link in all the required source files into the new project.

That will allow you to use the same source base from both ESD and Eclipse at the same time, with some manual project synchronization.

Copy the generated one into a subfolder called Project, edit in notepad, set up the paths to files in the project to PARENT-1-PROJECT_LOC, and use absolute paths for source files that are in the Libraries folder of your installation.

The #ifndef ESD_SIMULATION macro can be used to exclude any platform specific code, and put testing stubs in place instead.