Bug 371982

Summary: git master - during Project Monitor playback, vertical Timeline position changes automatically, though it shouldn't [video example included]
Product: [Applications] kdenlive Reporter: Unknown <null>
Component: User Interface & MiscellaneousAssignee: Jean-Baptiste Mardelle <jb>
Status: RESOLVED FIXED    
Severity: normal CC: null, oluja
Priority: NOR    
Version First Reported In: git-master   
Target Milestone: ---   
Platform: Other   
OS: Linux   
URL: https://youtu.be/CpQo59e_eig
Latest Commit: http://commits.kde.org/kdenlive/a6d10adf0c8df453cfbb765da4437132986a1b9d Version Fixed/Implemented In:
Sentry Crash Report:

Description Unknown 2016-11-02 17:21:12 UTC 
See video in URL field for example.

On my laptop display screen (1366x768), sometimes I want to look at the lower audio tracks during playback. The track height is set to the smallest possible in the timeline. However, when I hit SPACEBAR or press the play button to begin playback in the Project Monitor, the vertical position of the Timeline automatically moves and goes to the time-most track in the Timeline. Trying to use the vertical scrollbar on the right to see the lower tracks results in the same thing: the timeline veritcal position immediately goes back up to the top after releasing the left mouse button.

EXPECTED BEHAVIOR:
For the Timeline to stay on the vertical position you have it on during playback, and not to automatically adjust.

Bug discovered while using Kdenlive 16.11.70 git master build from ppa:kdenlive/kdenlive-master, Ubuntu 16.10 w/ Unity 7.5.0 desktop environment, KDE Frameworks 5.26.0, Qt 5.6.1.
Comment 1 Jean-Baptiste Mardelle 2016-11-02 22:55:17 UTC 
Git commit a6d10adf0c8df453cfbb765da4437132986a1b9d by Jean-Baptiste Mardelle.
Committed on 02/11/2016 at 21:24.
Pushed by mardelle into branch 'master'.

Fix unwanted vertical scrolling

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

http://commits.kde.org/kdenlive/a6d10adf0c8df453cfbb765da4437132986a1b9d
Comment 2 farid 2016-11-03 00:51:41 UTC 
*** Bug 371818 has been marked as a duplicate of this bug. ***