Bug 408636

Summary: The horizontal dividing line between the timeline and the top of the kdenlive window does not save the position after dragging down in Kubuntu 18
Product: [Applications] kdenlive Reporter: ITicDigger
Component: User Interface & MiscellaneousAssignee: Jean-Baptiste Mardelle <jb>
Status: RESOLVED FIXED    
Severity: grave CC: fritzibaby
Priority: NOR    
Version First Reported In: 19.04.2   
Target Milestone: ---   
Platform: Kubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description ITicDigger 2019-06-13 06:02:52 UTC 
STEPS TO REPRODUCE
1. Open kdenlive
2. Pull down the horizontal dividing line above the timeline, which determines the ratio between the height of the timeline and the project monitor.

OBSERVED RESULT
The dividing strip jumps back up is not. The height of the timeline does not decrease, the height of the project monitor does not increase.

EXPECTED RESULT
The dividing line should remain where I dragged it (lower than it was). The height of the timeline should decrease, the height of the project monitor should increase.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 18.04 64-bit
(available in About System)
KDE Plasma Version: 5.12.7
KDE Frameworks Version: 5.44.0
Qt Version: 5.9.5
Kdenlive appimage 19.04.2d_x86-x64

ADDITIONAL INFORMATION
This behavior is observed only on Kubuntu 18.04. Before that, he worked under Ubuntu Studio 04/18/1 (xfce) - the dividing line worked fine.
For me, this bug is critical, as it makes it impossible to quickly view clips in a window of sufficient size. By default, the dividing line is too high (above the middle of the window) due to which the project monitor becomes too small.
Comment 1 ITicDigger 2019-06-13 15:19:53 UTC 
Almost false alarm. The bug was not so serious, because everything is solved by re-launching kdenlive. On the second run, everything works fine.
Comment 2 emohr 2021-03-07 17:02:58 UTC 
Thank you for the feedback and contribution. Glad to hear it works. 

Yes there were "snap back" of the timeline in past version but this should now be fixed with the 20.12 version.

We close this bug. If it still appears in the latest version, please feel free to re-open it and update the affected version number.