Bug 358782 - 15.13 git master: cannot delete custom effects
Summary: 15.13 git master: cannot delete custom effects
Status: RESOLVED FIXED
Alias: None
Product: kdenlive
Classification: Applications
Component: User Interface & Miscellaneous (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR normal
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-30 16:55 UTC by Wegwerf
Modified: 2016-02-05 15: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 Wegwerf 2016-01-30 16:55:17 UTC
"Delete effect" in the context menu of a custom effect in the effects list has (pun intented) no effect; the effect cannot be deleted.

Reproducible: Always

Steps to Reproduce:
1. Create a new custom effect.
2. Choose "delete effect" from the context menu on the new custom effect.


Actual Results:  
Nothing happens. The custom effect does not get deleted.

Expected Results:  
Custom effect is deleted.
Comment 1 Wegwerf 2016-01-30 17:01:10 UTC
For a custom effect simply use, for instance, "fade from black" and save it as a custom effect.
Comment 2 lostinspacetime 2016-01-31 15:07:30 UTC
Same problem in 15.12
Comment 3 Jean-Baptiste Mardelle 2016-02-01 21:09:25 UTC
Git commit 1cd0854ec98e5dde713f8bfe693e1cbd287f6e1e by Jean-Baptiste Mardelle.
Committed on 01/02/2016 at 21:09.
Pushed by mardelle into branch 'master'.

Fix custom effects deletion

M  +1    -1    src/effectslist/effectslistview.cpp

http://commits.kde.org/kdenlive/1cd0854ec98e5dde713f8bfe693e1cbd287f6e1e
Comment 4 Jean-Baptiste Mardelle 2016-02-01 21:12:24 UTC
Git commit 47567f07dcfd0f68e0ec9ed31803dea250add203 by Jean-Baptiste Mardelle.
Committed on 01/02/2016 at 21:12.
Pushed by mardelle into branch 'Applications/15.12'.

Fix custom effects deletion

M  +1    -1    src/effectslist/effectslistview.cpp

http://commits.kde.org/kdenlive/47567f07dcfd0f68e0ec9ed31803dea250add203
Comment 5 Wegwerf 2016-02-05 15:04:54 UTC
Jean-Baptiste, thank you for fixing this. Works now, so I set this to resolved fixed.