[racket] moby: problem running on-tick and on-acceleration simultaneously on android

> It might be that the velocity calculations really need to be done from
> the Java side of things to get the right performance.  If that's the
> case, I can sketch out the extensions to Phonegap.

Perhaps my question was a bit too rash, I should perform some more tests before (at least before causing you more work :-; )
I'll try to come back with some more substantial result (in fact I didn't investigate if the problem was general CPU overload, or had to do with the simultaneous use of on-tick specifically)



> Moby is already
> doing something like this, because the "on-shake" handler's doing a
> kind of change-of-acceleration computation and the Phonegap extension
> is generating the on-shake event.


Thanks for the hint, I'l have a look! Just a general question: I understood like it was planned to revert to the "actual" phonegap code in the long run, but  here you're spending time extending the fork, so...
Just wondering in which direction you plan to go?

Thanks,
Sigrid