Note that there are some explanatory texts on larger screens.

plurals
  1. USUsul
    primarykey
    data
    text
    plurals
    1. COCertainly. Bad news is that those numbers where just the first stress test i did. I've now looked just how high it could go smoothly and it looks like it's almost my initial test. It gets stuttering at 3.000 points / 1 single chart / 100 msec refresh rate. Just edited results. The refactoring was an optimization focused really on speed not memory, speed is good, memory not so when we need real time refresh times.
      singulars
    2. COI'll check that but I did revert that specific issue and still found GC was a problem. I delved deeper into the code with Eclipses allocation tracker and saw plenty of other problematic areas regarding allocation on onDraw. I can rig a test with the official demo so we can look at the same problem if you're willing to look into it but it'll take some refactoring around object factories / pools to make Ace work real time on Android. Are you testing this in HoneyComb? GC changed completely to a concurrent GC algorithm so it might not be an issue on previous versions.
      singulars
    3. COMore potentially relevant info. The call used in the demo to add the view 'layout_eeg1.addView(view_eeg1); //, new LinearLayout.LayoutParams(LayoutParams.FILL_PARENT, LayoutParams.FILL_PARENT));' gets flagged as the constants are deprecated. I'm building against Android 4.2. IF I use something like LinearLayout.LayoutParams(200, 200) it does get centered. This is not a solution though as I'm fix the layout size and making it impossible to work for several devices.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload