| Summary: | Project Bin clip description not editable after adding Zone subclip | ||
|---|---|---|---|
| Product: | [Applications] kdenlive | Reporter: | David <rylleman> |
| Component: | User Interface & Miscellaneous | Assignee: | Jean-Baptiste Mardelle <jb> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | fritzibaby |
| Priority: | NOR | Flags: | fritzibaby:
Brainstorm+
|
| Version First Reported In: | 17.12.3 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
kdenlive 17.12.3 with description field
18.12.0e without description field Short film, 44sec, showing the issue |
||
|
Description
David
2019-01-03 11:30:39 UTC
Which description field do you mean. Can you upload a screenshot? Please try with the current Kdenlive AppImage version 18.12.0e With right click on the clips and click on Rename you can rename as you wish. Or click on the clip and hit F2. Created attachment 117321 [details]
kdenlive 17.12.3 with description field
Created attachment 117322 [details]
18.12.0e without description field
The description field in the bin has now disspaeared! I'll file a separate issue on that. Attached screenshots from both 17.12.3 and 18.12.0e showing this. Back to this issue, the same seems to be true for the name field. A clip without a child zone can be renamed. If a child is added the parent can no longer be renamed while the child can. The Description column can be shown or hidden from the bin menu. Just check it to make it re-appear. I can confirm the renme issue though. Sorry, disregard my previous comment, the fields were turned off... Here's a 44sec video showing the issue. https://www.dropbox.com/s/pz7tb5u1gy8zyly/kdenlive-descrition-field_no-edit.mp4?dl=0 Created attachment 117323 [details]
Short film, 44sec, showing the issue
Solved in refactoring and backported the fix to the stable 18.12 branch. Commit: https://cgit.kde.org/kdenlive.git/commit/?id=822d219c0691f13b657a22860a825a7b76c9b0a9 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. |