3 ms·
Good catch. We actually spent a while trying to figure out what caused that, but it was impossible for us to use our usual debugging technique of printing trac
by tnecniv 12y ago
Good catch.
We actually spent a while trying to figure out what caused that, but it was impossible for us to use our usual debugging technique of printing traces on since that breaks down when user input is involved. We stopped working on the project before we could squash that bug. It's the only remaining bug as far as we know.