Bug 359845

Summary: 15.13.0 git master - Can't get out of edit mode when playing project with a specific clip highlighted.
Product: [Applications] kdenlive Reporter: Unknown <null>
Component: User Interface & MiscellaneousAssignee: Jean-Baptiste Mardelle <jb>
Status: RESOLVED FIXED    
Severity: normal CC: null
Priority: NOR    
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Unknown 2016-02-26 22:22:10 UTC 
If you have a clip in the timeline with, say, the Pan and Zoom effect applied to it, the monitor goes into edit mode, right? Well, when you try to leave edit mode, then playback the project, it goes right back in to edit mode. Similarly, when you click the "edit mode" button to leave edit mode during playback, it goes right back into it.

Reproducible: Always

Steps to Reproduce:
1. Add a clip into the timeline
2. Apply an effect like Pan and Zoom to the clip
3. Click "Show/Hide Edit Mode" to disable edit mode, then playback project
OR
3. Plaback project, then click "Show/Hide Edit Mode".

Actual Results:  
Monitor should leave edit mode until the "Show/Hide Edit Mode" button is clicked again.

Expected Results:  
Monitor stays in edit mode as long as the clip with that effect is highlited.

Tested while using Kdenlive 15.13.0 git master build on Antergos Linux x64, KDE Plasma 5.5.4.
Comment 1 Jean-Baptiste Mardelle 2016-02-27 15:25:12 UTC 
Git commit 118cc504896d9e0b39704df4702dc66f7071c3b3 by Jean-Baptiste Mardelle.
Committed on 26/02/2016 at 23:25.
Pushed by mardelle into branch 'master'.

Fix several issues in monitor's effect scene enabling/disabling

M  +1    -1    src/effectstack/collapsibleeffect.cpp
M  +23   -10   src/effectstack/effectstackview2.cpp
M  +0    -10   src/effectstack/widgets/geometrywidget.cpp
M  +6    -2    src/monitor/monitor.cpp

http://commits.kde.org/kdenlive/118cc504896d9e0b39704df4702dc66f7071c3b3
Comment 2 Unknown 2016-03-02 16:53:50 UTC 
Works great now. Thanks JB! Marking this bug as fixed.