-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Layers/groups/paths duplicate when you are duplicating keyframes #324
Comments
I got time to record a video: duplicacting.mp4 |
I'm unable to reproduce this issue in 1.0.0-beta1, the only problem I found was that keyframe selection would not get removed after clicking on the viewport which leads to confusing behaviour Doing the same, getting no object + keyframe duplication, only keyframe duplication: |
Then it only happens in macOS... @KirbysDarkNebula, what OS are you using? |
I'm using Linux with the Appimage release |
Thanks! |
In some scenarios you want to duplicate keyframes and you end up duplicating layers/groups/paths as well.
For instance, if you select a square in the viewport and then you go to the keyframes timeline, select a keyframe, scrub the "time line" and duplicate (by menu or shortcut) the result is that you are duplicating both the path and creating a duplicate of the keyframe...
Following this example, if you select a square in the viewport (it gets selected in the timeline) but you first click in an empty space then you are kind of "unselecting all". Now you go back to the keyframes timeline, select a keyframe, scrub the "time line" and duplicate (by menu or shortcut) the result is now is correct, just the keyframe gets duplicated.
The proposed behavior here would be that if your mouse is in the timeline, if you run the "duplicate" command, if there is a keyframe selected the only thing that gets duplicated is the keyframe and not any other thing but keyframes. In case there is no keyframe selected then it could duplicate layers/groups/paths...
Could you reproduce this?
Thanks!
The text was updated successfully, but these errors were encountered: