18:04:54 - Bollebib: if you select a range of 20 frames 18:05:08 - Bollebib: and then increase HOLD FRAMES by a large amount 18:05:21 - Bollebib: everything that would surpass the timeline that is visible 18:05:23 - Bollebib: gets deleted 18:17:10 - tiar: Bollebib: yeah I belive it is what happens So select a range of 20 frames and attempt to add many hold frames ->everything the timeline doesnt auto-expand to fit those frames and they get lost in the void.
I cannot reproduce this in the nightly builds. I selected 8 hold frames, input 30, and that results in each of the frames getting a hold of 30 frames inbetween, going off the visible canvas. Can you check again with the nightlies?
https://www.youtube.com/watch?v=tyLnDSvGX64&feature=youtu.be tested in the current nightly it still happens I go over details in the video
Git commit e1be1dad8f0c5d2149338b818ce38a5326cfca16 by Scott Petrovic. Committed on 01/04/2019 at 23:30. Pushed by scottpetrovic into branch 'master'. M +1 -1 plugins/dockers/animation/timeline_frames_model.h M +26 -0 plugins/dockers/animation/timeline_frames_view.cpp https://commits.kde.org/krita/e1be1dad8f0c5d2149338b818ce38a5326cfca16