Utility problem with setWatch

Oh, interesting. Thanks for helping enhance my imagination. So by measuring the pulse width, you can get a sense of the signal's "speed" on a pseudo-instantaneous basis. That's cool.

Still, I do feel that the default mode should be more obviously correct, with a mode to measure pulse-width available as a non-default option. +1 on efficiency and memory. Also, the same thing for developer time, if those two aren't in conflict.

What if...

• when edge:rising or edge:falling, default to event-orientation, unrolling the trivial workaround to non-developer responsibility
  
• when pulseWidth: true, additionally include pulseWidth or lastChangeTime in the event
  
  

WDYT?

R