I have fixed compatibility with apiLevel < 2.4. It should now work correctly.
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Quote from: DJ Omnimaga on April 01, 2016, 03:45:27 PMTell me what I need to fix to make it work correctly. Also I updated it so check that version to see if that works correctly.
It doesn't run at all on OS 3.6
Quote from: Jim Bauwens on April 01, 2016, 09:49:31 AMI wasn't expecting it to run fast at all on an actual handheld device.
I've tested it on my handheld, but sadly rendering per frame takes a couple of seconds. You probably tested on the computer or iPad software? Edit: I see that you mentioned this in your readme.
Quote from: Jim Bauwens on April 01, 2016, 09:49:31 AM
Looking at the code, you should try to avoid making tables to store data during rendering, as allocating data from the heap is an expensive operation. Of course, it does become more complex that way to store (for example) vector points, but you really do get a good speedup. The price being that your code gets larger and more messy. If you can avoid certain function calls, you should do that too.