You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I agree that all basic demos should be hardware independent and run in emulator.
This demo is currently as I got it, so there might be some issues.
For me it runs fine in the emulator if I clock 'Continue' on the exceptions.
It look like it creates a bunch of files with different sizes, and creates huge byte arrays to do so.
On the first run it will calibrate the touch and exit then. The 2nd run will start the actual app.
A couple of nice and actually working demos are on my list.
btw. I prefer testing on real hardware, because the performance of the emulator is horrible.
Tried downloading the current code, and it compiles fine, but a required hw setup needs to go into an emulator.config.
I think it writes to files, and requires decent amounts of memory, not sure though what else could be required.
For developing a gui, running in an emulator in the first phases are often preferable.
The text was updated successfully, but these errors were encountered: