Bug 362592 - git master: trying to set region to whole clip removes region
Summary: git master: trying to set region to whole clip removes region
Status: RESOLVED NOT A BUG
Alias: None
Product: kdenlive
Classification: Applications
Component: User Interface (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-02 16:42 UTC by Wegwerf
Modified: 2016-05-09 16:51 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Wegwerf 2016-05-02 16:42:50 UTC
When trying to select the whole clip as a region (for instance, for following insert), Kdenlive instead delects/removes the current region.

Reproducible: Always

Steps to Reproduce:
1. Create new project.
2. Create/add clip; e.g. create color title clip.
3. Select clip.
4. Move clip monitor playhead to start of clip, set in point.
5. Move clip monitor playhead to end of clip, set out point.

Actual Results:  
No clip region set.

Expected Results:  
Clip region should be set to cover whole clip.
Comment 1 Jean-Baptiste Mardelle 2016-05-03 19:31:56 UTC
If you select a whole clip, the zone is effectively not shown in the clip monitor ruler, because the whole clip is selected, so there is no real zone selection.

Is this a problem ? I don't really see a bug here...
Comment 2 Wegwerf 2016-05-03 20:42:41 UTC
When I need to insert or overwrite a complete (short) clip into the timeline this currently is not possible.
Comment 3 Jean-Baptiste Mardelle 2016-05-03 21:02:55 UTC
I cannot reproduce. Can you describe the exact steps that lead to the bug ?
Comment 4 Wegwerf 2016-05-09 16:51:36 UTC
I was under the wrong impression that it seemed to be impossible to select the whole bin clip. In fact, it is possible, but then no zone indication is shown. Inserting the whole clip using key V with timeline zone disabled when works as expected. For this reason I'm closing this bug as RESOLVED INVALID -- so we have less bug report noise.