https://bugs.kde.org/show_bug.cgi?id=459455
--- Comment #4 from Maarten <[email protected]> --- I'm forgetting one important thing which is probably even the most important one which is making the current workflow unrealistic: We seldom know the amount of frames to make blank or overwrite. And even if we think we know the amount we will still check it first before overwriting other work to be 100% sure we don't loose existing frames. It's pretty time consuming and error prone, but I think even unrealistic in lots of cases, to count frames in the timeline to know what number to fill in here. Try counting 50 frames in the timeline without making an error... And than you can be happy if you don't need to scroll the timeline. AND rely on your counting afterwards, because if you made a mistake, you loose work. I think this workflow counts to much on straight ahead animation (adding frames after the last frame). But most animators work with "pose to pose" methods most of the time (so create keyframes on the important poses, and than start to fill in the frames within that range. When animating "straight ahead" it's not really an issue to insert just a number of frames. But when adding the blanks within we must have an exact frame count to not overwrite the already added keyframes. So this makes this method not very realistic in real world usages when using pose-to-pose. Hope this makes sense. -- You are receiving this mail because: You are watching all bug changes.
