Anthony

At this point you should: - add the other signed mem arrays (mem16, etc) - update docs\api\api-ts-memory.md

> Or is there some other deprecated section I missed? I think that's. I think `memF `should be removed from that section as well? The intent I am going after...

is there a difference between "nightly" and "developer". "Nightly" would not be good to use for testing. "developer" might be okay. We could also just add instructions to the debug...

People generally just want to test theri code with stable releases, otherwise you don't know whos bug it is.

Leave the issue open. Maybe updated the test output so that the "known won't work on other platforms" tests are grouped together with a heading like "These may fail on...

`WaitForDrawSeqToComplete` seems like a simple solution. Another, more backwards compatible options would be to add `twrConDrawSeqNoWait`. (or `twrConDrawSeqAsync` at the risk of overusing the term Async)

good point. But the same issue exists with the C APIs (how to get the benefits of noBlock without breaking existing apps). Regarding your 2nd questions -- here is some...

i started looking into this, it is probably related to my recent event changes. it appears that the animationFrame event triggers while the twrConDrawSeq is processing (or perhaps after if...

upon further investigation, it appears that what is happening is this: When (the synchronous) twrConDrawSeq is called (the twrConDrawSeq was triggered by a the flush to measure text)., it waits...

this is pretty complicated. What with nested blocking waits. Ie, a callback that is called while a a blocking wait is waiting, and the callback does a blocking wait. I...