dwitter.net

+ New dweet
function u(t) {
} //
122/140


Please log in (or register) to post a dweet (copy-paste the code somewhere safe to save it meanwhile)


u(t) is called 60 times per second. t: Elapsed time in seconds. S: Shorthand for Math.sin. C: Shorthand for Math.cos. T: Shorthand for Math.tan. R: Function that generates rgba-strings, usage ex.: R(255, 255, 255, 0.5) c: A 1920x1080 canvas. x: A 2D context for that canvas.
show FPS hide FPS share 1 remix fullscreen

function u(t) {

}//
140/140


Please log in (or register) to post as a new dweet (copy-paste code somewhere safe to save it meanwhile).

  • u/taupelink
    Note: This dweet looks different on different browsers.You may see a blank column on the left edge and just to the right of center. Those were not there when I composed the dweet on iOS. They can be eliminated by replacing m-m%4 at the end with m-m%4+(m%4?0:7)
  • u/taupelink
    I think what's happening is, different environments interpret arc differently in case the start and end angles are the same. In iOS, a full circle is drawn (which is what I intended). Elsewhere, nothing is drawn (hence the white columns you may be seeing).
  • u/pavel
    As far as I know it is just Safari that has a bug with arc, where the two angle terms do not simply get %(2*pi) treatment. If the angles are sufficiently large, like 10pi-ish, the arc breaks and draws weird lines. So you have to ensure the angles are small manually :/
  • u/taupelink
    well, the question here is what happens when the angle difference is zero? I suspect this is another quirk of Safari/iOS: when the angle is zero, it defaults to drawing a full circle.

Please log in (or register) to comment.

u(t) is called 60 times per second. t: elapsed time in seconds. c: A 1920x1080 canvas. x: A 2D context for that canvas. S: Math.sin C: Math.cos T: Math.tan R: Generates rgba-strings, ex.: R(255, 255, 255, 0.5)