anchor.diff:  
   |As described <<cues#held-flag,above>>, causes the cue's effect to run only
   as long as the corresponding controller button or pad is held down, if
  -the controller supports that capability. Currently the web interface
  -does not, but the
  +the controller supports that capability. All current
  +controller implementations, including the web interface, the
   http://deepsymmetry.org/afterglow/doc/afterglow.controllers.ableton-push.html[Ableton
  -Push mapping] does, as do mappings to generic MIDI controllers created using
  -http://deepsymmetry.org/afterglow/doc/afterglow.show.html#var-add-midi-control-to-cue-mapping[afterglow.show/add-midi-control-to-cue-mapping].
  +Push mapping], and mappings to generic MIDI controllers created using
  +http://deepsymmetry.org/afterglow/doc/afterglow.show.html#var-add-midi-control-to-cue-mapping[afterglow.show/add-midi-control-to-cue-mapping],
  +do honor this setting.
   
   |`:variables`
   |none
  
positive.code: |`:held`
  |`false`
  
  |As described <<cues#held-flag,above>>, causes the cue's effect to run only
  as long as the corresponding controller button or pad is held down, if
  the controller supports that capability. Currently the web interface
  does not, but the
  http://deepsymmetry.org/afterglow/doc/afterglow.controllers.ableton-push.html[Ableton
  Push mapping] does, as do mappings to generic MIDI controllers created using
  http://deepsymmetry.org/afterglow/doc/afterglow.show.html#var-add-midi-control-to-cue-mapping[afterglow.show/add-midi-control-to-cue-mapping].
  
  |`:aftertouch`
  |`false`
  
negative.code: corresponding controller pad is held down (this is done by passing a
  true value with the `:held` optional keyword argument when creating
  the cue). This is often done for intense effects like strobes.
  
  Cues can also offer pressure sensitivity on controllers which support
  this (like the Ableton Push). For such cues, one or more variable used
  