Corrosive

Simply put:  when trying to copy/paste properties between keyframes, the property field being copied from/pasted too will catch the key event (and mess up your animation) unless you've cleared focus by clicking somewhere outside the field.  This is compounded somewhat by the fact that pressing enter/return while an input is focused doesn't clear focus as with many applications.
 
For this reason, timeline controls are ideally constrained to keys that are considered invalid inputs on the most commonly used input fields.
 
IMO, the "QWERT" row would be much better suited for timeline manipulation, though I suppose it could also be a togglable(toggleable?) option.

Simply put:  when trying to copy/paste properties between keyframes, the property field being copied from/pasted too will catch the key event (and mess up your animation) unless you've cleared focus by clicking somewhere outside the field.  This is compounded somewhat by the fact that pressing enter/return while an input is focused doesn't clear focus as with many applications.
 
For this reason, timeline controls are ideally constrained to keys that are considered invalid inputs on the most commonly used input fields.
 
IMO, the "QWERT" row would be much better suited for timeline manipulation, though I suppose it could also be a togglable(toggleable?) option.

Simply put:  when trying to copy/paste properties between keyframes, the property field being copied from/pasted too will catch the key event (and mess up your animation) unless you've cleared focus by clicking somewhere outside the field.  This is compounded somewhat by the fact that pressing enter/return while an input is focused doesn't clear focus as with many applications.
 
For this reason, timeline controls are ideally constrained to keys that are considered invalid inputs on the most commonly used input fields.
 
IMO, the "QWERT" row would be much better suited for timeline manipulation, though I suppose it could also be a togglable(toggleable?) option.

Simply put:  when trying to copy/paste properties between keyframes, the property field being copied from/pasted too will catch the key event (and mess up your animation) unless you've cleared focus by clicking somewhere outside the field.  This is compounded somewhat by the fact that pressing enter/return while an input is focused doesn't clear focus as with many applications.
 
For this reason, timeline controls are ideally constrained to keys that are considered invalid inputs on the most commonly used input fields.
 
IMO, the "QWERT" row would be much better suited for timeline manipulation, though I suppose it could also be a togglable(toggleable?) option.

Simply put:  when trying to copy/paste properties between keyframes, the property field being copied from/pasted too will catch the key event (and mess up your animation) unless you've cleared focus by clicking somewhere outside the field.  This is compounded somewhat by the fact that pressing enter/return while an input is focused doesn't clear focus as with many applications.
 
For this reason, timeline controls are ideally constrained to keys that are considered invalid inputs on the most commonly used input fields.
 
IMO, the "QWERT" row would be much better suited for timeline manipulation, though I suppose it could also be a togglable(toggleable?) option.

Simply put:  when trying to copy/paste properties between keyframes, the property field being copied from/pasted too will catch the key event (and mess up your animation) unless you've cleared focus by clicking somewhere outside the field.  This is compounded somewhat by the fact that pressing enter/return while an input is focused doesn't clear focus as with many applications.
 
For this reason, timeline controls are ideally constrained to keys that are considered invalid inputs on the most commonly used input fields.
 
IMO, the "QWERT" row would be much better suited for timeline manipulation, though I suppose it could also be a togglable(toggleable?) option.

Simply put:  when trying to copy/paste properties between keyframes, the property field being copied from/pasted too will catch the key event (and mess up your animation) unless you've cleared focus by clicking somewhere outside the field.  This is compounded somewhat by the fact that pressing enter/return while an input is focused doesn't clear focus as with many applications.
 
For this reason, timeline controls are ideally constrained to keys that are considered invalid inputs on the most commonly used input fields.
 
IMO, the "QWERT" row would be much better suited for timeline manipulation, though I suppose it could also be a togglable(toggleable?) option.

Simply put:  when trying to copy/paste properties between keyframes, the property field being copied from/pasted too will catch the key event (and mess up your animation) unless you've cleared focus by clicking somewhere outside the field.  This is compounded somewhat by the fact that pressing enter/return while an input is focused doesn't clear focus as with many applications.
 
For this reason, timeline controls are ideally constrained to keys that are considered invalid inputs on the most commonly used input fields.
 
IMO, the "QWERT" row would be much better suited for timeline manipulation, though I suppose it could also be a togglable(toggleable?) option.

Simply put:  when trying to copy/paste properties between keyframes, the property field being copied from/pasted too will catch the key event (and mess up your animation) unless you've cleared focus by clicking somewhere outside the field.  This is compounded somewhat by the fact that pressing enter/return while an input is focused doesn't clear focus as with many applications.
 
For this reason, timeline controls are ideally constrained to keys that are considered invalid inputs on the most commonly used input fields.
 
IMO, the "QWERT" row would be much better suited for timeline manipulation, though I suppose it could also be a togglable(toggleable?) option.