Bug 368569 - git master - After I click+drag video from Monitor to Timetline, Clip Monitor starts playing video... though it shouldn't.
Summary: git master - After I click+drag video from Monitor to Timetline, Clip Monitor...
Status: RESOLVED FIXED
Alias: None
Product: kdenlive
Classification: Applications
Component: User Interface & Miscellaneous (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords:
: 366574 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-09-10 20:59 UTC by Unknown
Modified: 2016-09-11 20:04 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Unknown 2016-09-10 20:59:18 UTC
When I have a video or sound clip in the Clip Monitor, and I left+click and drag it into the timeline, after I drop the clip in the timeline the Clip Monitor starts playing automatically, though it shouldn't.

Reproducible: Always

Steps to Reproduce:
1. Open video/sound clip in Clip Monitor
2. Click+drag clip into timeline

Actual Results:  
Clip Monitor starts playing back video/sound clip automatically without anything being pressed.

Expected Results:  
Clip monitor shouldn't be playing automatically after click+drag clip into timeline.

Bug discovered using Kdenlive 16.11.70 git master build from ppa:kdenlive/kdenlive-master.

Ubuntu GNOME 16.10 beta 1, Gnome 3.20 desktop environment.

Qt 5.6.0
KDE Frameworks 5.24.0
Comment 1 Jean-Baptiste Mardelle 2016-09-11 19:58:34 UTC
Git commit bed3443687b4115bab2ed86a1a6b88d3771e8680 by Jean-Baptiste Mardelle.
Committed on 11/09/2016 at 19:58.
Pushed by mardelle into branch 'Applications/16.08'.

Fix clip monitor starting to play after drag

M  +8    -4    src/monitor/glwidget.cpp
M  +7    -5    src/monitor/monitor.cpp

http://commits.kde.org/kdenlive/bed3443687b4115bab2ed86a1a6b88d3771e8680
Comment 2 Jean-Baptiste Mardelle 2016-09-11 20:04:28 UTC
*** Bug 366574 has been marked as a duplicate of this bug. ***