Trace update/odd buffer behaviour

Bag2, i have no words to thank you for this result: it works like a sharm! For this bug i was seriously thinking to ask for refund, but with your work you changed this stuff in something useful.
I hope that at seeedstudio someone will understand how important this fix is and will include it in the next official release.

Are you thinking about to share the source code? i’m really curious to compare it with the original to see exactly where the issue come from.

And just about the code: from the official source code it seems that Sync. Mode “NONE” does exactly the same as “SCAN” (from Process.c):


break;
case NONE:
case SCAN:
__Set(TRIGG_MODE, UNCONDITION);
Process();
break;

as after “case NONE:” there’s no “break” statement (i guess this’s another bug); hence, why not using NONE mode to implement your fix, leaving the original behaviour in SCAN? or maybe i’m missing something and NONE mode is really different from SCAN?

Thanks again.