https://bugs.kde.org/show_bug.cgi?id=520205

Emmet O'Neill <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|CONFIRMED                   |RESOLVED
         Resolution|---                         |NOT A BUG
                 CC|                            |[email protected]

--- Comment #3 from Emmet O'Neill <[email protected]> ---
GlitchedDragon is right. This is intended behavior based on the assumption that
people want to have the timeline zoomed to an appropriate size for the
animation that they're working on. 

It's actually a combined effect of 2 animation settings:

1. Krita Settings > General > Animation > "Automatically adapt playback range
to keyframes".

This setting will adjust the playback range of your animation to any new
keyframe that you create outside of the current playback range. If you have a
playback range from frame 0-15, and you make a new keyframe on 20, the playback
range will extent to 20 to include the new frame. If you don't want it to do
that, you should disable this option.

2. Krita Settings > General > Animation > "Automatically zoom timeline to fit
playback range".

This setting will change the zoom level of your timeline to best fit the size
of your animation playback range. If you set a small playback range of just a
few frames, the animation timeline will zoom in to accommodate. And if you set
a large playback range, the timeline will zoom out. If you don't want it to do
that, disable that one.

In other words, when you create/copy a new frame outside of the playback range
of your animation, option 1 is automatically extending the range and option 2
is automatically zooming the canvas to fit that range. Because you can
customize this behavior to your preference by mixing and matching either or
both of those settings, this is not a bug.

(NOTE: I should add that there is a minor bug related to the timeline zooming,
where *sometimes* the zooming function does not scroll to the correct position,
but that is a separate known problem that's slightly more complicated to fix at
the moment and may require a patch to Qt's slider behavior.)

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to