Actually about the joystick, i experience a slowdown even just connecting it, without even any code to attach callbacks etc.
I don't know, maybe the system is already almost saturated and that's enougth to tip it over?
Anyway, i give a serious try with multicore, to distribute the load to different cores, but i don't seem to be able to make it run.
What i see is that the program runs and only code with core = 0 on my CMultiCoreSupport class gets run.
My steps were: I recompiled circle with ARM_ALLOW_MULTI_CORE (which is confirmed becouse the class CMultiCoreSupport is there). I made a subclass of it with some minimal stuff just to see it working (like logging nCore or drawing to screen), i initialized it after all other initializations on core 0.
Then on main kernel.cpp Run method i called myclass.Run(0) (as on sample 17). I'm not sure why this is correct, wouldn't it just run the class with parameter nCore set to 0? Perhaps core 0 is run this way and 1, 2, 3 starts by themselves somehow?
I fumbled about on multicore.cpp, noticed the "main_secondary" which sounds like an entry point for secondary cores. Not sure who calls it?
Anyway, am i missing something? Looks like there's something to trigger execution of other cores but the more i look at example 17 the more it seems i'm doing exacly the same stuff.
PS i'm running inside circle-stdlib if that can help. And no joystick attached.