Bug 364836

Summary: git master: after you insert 2 clips at the beginning of an empty timeline if you trim the second clip it jumps forward
Product: [Applications] kdenlive Reporter: Massimo Stella <maxstar>
Component: User Interface & MiscellaneousAssignee: Jean-Baptiste Mardelle <jb>
Status: RESOLVED FIXED    
Severity: normal CC: wegwerf-1-2-3
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Massimo Stella 2016-06-27 23:36:07 UTC 
If you insert 2 clips at the beginning of an empty timeline and you trim the second clip, by dragging the selection tool starting at the IN point, it jumps forward.

Reproducible: Always

Steps to Reproduce:
1. Open a new project and import one clip and set the timeline in "Strict mode"
2. Open the imported clip in the clip monitor and select a zone.
3. Click two times on the insert button located in the timeline toolbar, so that the first inserted clip is the second on the timeline.
4. By dragging the Selection tool, trim the second clip on the timeline by starting from its IN point: the clip will jump forward of the same lenght of the of the clip.

Actual Results:  
The second clip on the timeline will jump forward of the same lenght of the of the clip.

Expected Results:  
The clip is trimmed by the number of frames you dragged the mouse.
Comment 1 Jean-Baptiste Mardelle 2016-06-29 08:21:28 UTC 
Git commit c10f66e0096a9770e85a66ba63eaab082c56c152 by Jean-Baptiste Mardelle.
Committed on 29/06/2016 at 08:21.
Pushed by mardelle into branch 'master'.

Fix corruption on insert with grouped clips

M  +8    -0    src/timeline/customtrackview.cpp

http://commits.kde.org/kdenlive/c10f66e0096a9770e85a66ba63eaab082c56c152
Comment 2 Wegwerf 2016-07-15 19:33:38 UTC 
Massimo, is this fixed now for you?
Comment 3 Massimo Stella 2016-07-16 12:01:22 UTC 
Yes it is.
It was already ok after the first fix Jean-Baptiste done.
Comment 4 Wegwerf 2016-07-16 12:24:01 UTC 
Massimo, can you please then close this bug as resolved fixed? Thank you very much!