Pdr failure preventing the user from handling the keyframe. You set a certain amount of keyframes and later you will review the times (visually) at each position. After approaching 2 icons of keyframes, they come together and thereThe pdr prevents navigation via "next keyframe" or "previous keyframe".

In the example posted here, you can not navigate using "next keyframe" from the 4th keyframe, since the pdr allowed you to join keyframes in the previous pass. It is difficult to rebuild to show the bug.

The biggest problem I am facing in the pdr is that the lack of clear rule generatesConfusion and consequence. In my understanding it is a bug, because allowing actions that block navigation is open port to the "unknown" and then the user will use error and attempt to reach a solution.

Lack of rule in magic motion:

_How many keyframes are allowed?

_There should be a time reader for the keyframe set, so that it can inform the user of the time helping to resize (time) the imageTo build the "magic motion" coherent.

Today pdr fails to allowControls that slide and depending on the amount becomes difficultPositioning the icons of the "timeline keyframe" sensibly and allows you to disrupt keyframes neighbors.

When you hover the mouse in the keyframe timeline, sometimes an arrow appears on the mouse and sometimes a little hand appears. What is the meaning of this?

When you start creating the keyframes, it looks like the little hand indicates a region where no more keyframes can be added and the arrow would indicate that it is allowed to create keyframes.

But in the position where the project that I haveYou can see arrows only that pdr does not allow adding more keyframes.This has either a lack of clear rules or a bug. Both featureWhich Cyberlink should repair.In the example that I posted, I imagine that for solution I should delete many keyframes, then rebuild it. But how much time the user losesWith the lack of defined rules?

Thanks and sorry for my bad English, which comes from the Google translator.