when time (ticks) go backwards Timer overflows

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None

      ... which can be a problem on VMs. This leads to huge values being reported in seconds/millis/minutes when the unsigned micros() value gets converted to signed integer values.

      Potential solution - signed ticks?

      We should also warn the user when this is potentially detected now() - old > 1/2 the range.

            Assignee:
            Greg Studer (Inactive)
            Reporter:
            Greg Studer (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: