Document differences between keyframe and track deletion.

[mattdawkins]

trafficstars

When I heard that 'k' keyword is delete a keyframe, but that actually deletes boxes in a track, this doesn't sound right to me where a keyframe deletion wouldn't necessarily correspond to deleting the boxes in a track just a keyframe

[subdavis]

Could you specify the section of the docs that is related to this issue? The quoted phrases above do not appear in the docs.

[mattdawkins]

That's the problem, so people don't know if there's a shortcut for deleting a single track state

[subdavis]

k is the appropriate key for deleting a single track state.

If a track state is interpolated, it isn't a real track state and there is no reasonable way of removing it, IMO.

Something resembling "remove an interpolated track state" would have to involve one of the following, and all are bad options (again, IMO).

1. turning interpolation off for the full range, which there is another button for, and there could be a dedicated key for. I don't support having a button that deletes a keyframe or disables interpolation depending on context, because I think this would be really surprosing behavior.
2. deleting an interpolated track state by actually adding new surrounding keyframes to force a middle gap, which would be the most surprising behavior.

I don't believe that any internal or external users have asked us to do any of those things.

Action items

• wait for more feedback from the most recent person who asked for clarification on deletion.
• possibly add definitions of keyframe, feature, annotation, and track state to the docs.
• Possibly modify the text for the k shortcut in the application help and docs.

I don't think there are behavior or UI changes needed.

[subdavis]

related to #190

[waxlamp]

• possibly add definitions of keyframe, feature, annotation, and track state to the docs.
• Possibly modify the text for the k shortcut in the application help and docs.

@subdavis, these two items still feel legit. If they are, could you file new issues for them, and then close this one? Otherwise, closing this issue seems like the right thing at the moment.

[subdavis]

I've changed the title of this issue to make the documentation changes quoted above. Those will close this issue.