Bug 362900

Summary: git master: dropping clip in insert mode at the exact beginning of a clip causes alert "Cannot find clip to cut"
Product: [Applications] kdenlive Reporter: Wegwerf <wegwerf-1-2-3>
Component: User Interface & MiscellaneousAssignee: Jean-Baptiste Mardelle <jb>
Status: RESOLVED FIXED    
Severity: normal    
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: example kdenlive project with aux svg clips

Description Wegwerf 2016-05-10 18:04:41 UTC 
(While in insert mode) (dropping a clip using the mouse exactly at the beginning of a clip in the timeline) (causes the alert "Cannot find clip to cut").

(Hopefully,) (the parenthesis above help breaking down into its logical components.)

Reproducible: Always

Steps to Reproduce:
1. Open the attached example project.
2. Switch into insert mode.
3. Drag, say, clip 1.svg from the project bin into the timeline onto the middle track. Make sure to drop clip 1 exactly on the beginning of clip 2 in the timeline.

Actual Results:  
While clip 1 gets properly inserted without splicing clip 2 in the timeline, Kdenlive complains about "Cannot find clip to cut". Similar, a following undo complains about "Cannot find clip to uncut".

Expected Results:  
Kdenlive keeps silent and doesn't complain about "Cannot find clip to cut".
Comment 1 Wegwerf 2016-05-10 18:05:36 UTC 
Created attachment 98882 [details]
example kdenlive project with aux svg clips
Comment 2 Jean-Baptiste Mardelle 2016-05-10 20:10:54 UTC 
Git commit 7b444a78c69f554e8f82afb32994655cd84f8f51 by Jean-Baptiste Mardelle.
Committed on 10/05/2016 at 20:10.
Pushed by mardelle into branch 'master'.

Don't try unneeded cuts on insert

M  +17   -15   src/timeline/customtrackview.cpp

http://commits.kde.org/kdenlive/7b444a78c69f554e8f82afb32994655cd84f8f51
Comment 3 Wegwerf 2016-05-13 15:42:44 UTC 
Thank you very much, Jean-Baptiste! Works like a charm, so I can close this bug as RESOLVED FIXED.