Unlike the other toggle commands, val edit, being the "default" toggle, always turns other modes off. So you can't switch directly from some other kind of edit to val edit.

Toggle kbd entry mode, putting a K in the edit box as a reminder. This is orthogonal to the previous edit modes.

If the TimeStep is AbsoluteMark or RelativeMark, set its rank. Otherwise, set it to the deflt. This means the marklist names are sticky, so if you set it manually the default bindings won't mess it up.

Toggle between absolute and relative mark step.

Different from cmd_insert_time and cmd_delete_time since it only moves some events. Move back the next event, or move forward the previous event. Move the next or previous event for a point selection, or the selected events.

Extend the events in the selection to either the end of the selection or the beginning of the next note, whichever is shorter.

If the selection is on an event, the previous or next one (depending on Types.Orientation) is extended instead. This is more useful than reducing the event to 0, which has its own cmd anyway. If the selection is between a positive and negative event, the one corresponding to Sel.orientation is selected.

Toggle duration between zero and non-zero.

If the event is non-zero, then make it zero. Otherwise, set its end to the cursor. Unless the cursor is on the event start, and then extend it by a timestep.

Also I previously used the same event selection strategy as cmd_set_duration, which avoided the awkward point selection on zero-dur event case, but it turned out to be unintuitive to use in practice, because to toggle an event I'd have to put the selection on the next event.

Move only the beginning of an event. As is usual for zero duration events, their duration will not be changed so this is equivalent to a move.

Other cmds are biased towards the previous event, i.e. they affect the previous event if nothing is selected. This cmd is a little different: if it overlaps with an event, it will affect that one. Otherwise, it affects the next positive event or the previous negative event. The idea is that it's not very useful to clip an event to 0 by moving it past its end, so let's not do that. So it's like set_duration backwards: at does nothing, otherwise get next positive or prev negative.

Unlike cmd_set_duration, I can't think of a way for this to make sense with a non-point selection, so it uses the point position.

TODO for zero duration events, this is equivalent to cmd_move_event_backward. I'm not totally happy about the overlap, is there a more orthogonal organization?

Modify event durations by applying a function to them. 0 durations are passed through, so you can't accidentally give control events duration.

If there is a following event, delete it and extend this one to its end.

Since 0 dur events are never lengthened, joining control events simply deletes the later ones.

If it's a point, only join up to (and including) the nearest event start. Otherwise, if there's a collapsed pitch track and the next event doesn't have a pitch event, it's easy to wind up deleting a distance pitch and not noticing.

Split the events under the cursor.

Insert empty space at the beginning of the selection for the length of the selection, pushing subsequent events forwards. If the selection is a point, insert one timestep.

Remove the notes under the selection, and move everything else back. If the selection is a point, delete one timestep.

Delete the time range for all tracks in the block.

If the insertion selection is a point, clear any event under it. If it's a range, clear all events within its half-open extent.

Toggle the note duration between the end of the block, and the current time step.

Strip off the first transformer, and then the generator.

Handle UpdateInput that comes back from the floating input.

A leading space will create a zero duration event.

This will be fooled by a | inside a string, but I'll fix that if it's ever actually a problem.