Bug 377184 - Load Title default path is not taken from previous load
Summary: Load Title default path is not taken from previous load
Status: RESOLVED FIXED
Alias: None
Product: kdenlive
Classification: Applications
Component: User Interface (show other bugs)
Version: 18.08.2
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords: junior-jobs
Depends on:
Blocks:
 
Reported: 2017-03-04 01:28 UTC by Phuoc
Modified: 2019-01-06 12:31 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
fritzibaby: Brainstorm+
fritzibaby: low_hanging+


Attachments
Load Title dialog (16.96 KB, image/png)
2017-03-04 01:28 UTC, Phuoc
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Phuoc 2017-03-04 01:28:18 UTC
Created attachment 104356 [details]
Load Title dialog

Win7x64 16.12.1
Load title path is defaulted to the same location every time.

Steps:
1) New project.
2) Add title clip and load an existing title from a location other than kdenlive directory.
3) Add 2nd title clip.
The Load Title dialog is still defaulted to the kdenlive directory, see screenshot.

See also initial G+ discussion:
https://plus.google.com/109117066657466745395/posts/VSHZo7wVgWd
Comment 1 emohr 2018-10-13 09:45:29 UTC
Kdenlive should remember the path of the previous title loaded. If not, then this is a bug. There is no configuration option for a default path.

Please try with the actual Kdenlive version 18.08.2
Comment 2 emohr 2018-10-21 10:53:02 UTC
Moved to phabricator:

https://phabricator.kde.org/T9905
Comment 3 Phuoc 2018-10-21 22:37:25 UTC
Tried on v18.08.2, still the same issue.
Comment 4 emohr 2018-10-22 18:32:06 UTC
Thanks for testing. Opened a task to solve it.
Comment 5 emohr 2019-01-06 12:31:04 UTC
Should be solved with this commit: https://phabricator.kde.org/R158:c6adbe259e129588dad6c4229b5e60de62e3be77

Will come with the next release.

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