Bug 419863 - No more Wipe Method options in Transitions - Wipe 19.12.3 for Windows
Summary: No more Wipe Method options in Transitions - Wipe 19.12.3 for Windows
Status: RESOLVED DUPLICATE of bug 423619
Alias: None
Product: kdenlive
Classification: Applications
Component: User Interface & Miscellaneous (show other bugs)
Version: 19.12.3
Platform: Other Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: Jean-Baptiste Mardelle
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-04-09 02:26 UTC by kvkv
Modified: 2021-02-19 22:06 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:
fritzibaby: timeline_corruption+

Attachments
No Image file option in Transitions - Wipe 19.12.3 for Windows (125.35 KB, image/png)
2020-04-09 02:26 UTC, kvkv 		Details
Wipe method no more options (102.99 KB, image/png)
2020-04-09 02:53 UTC, kvkv 		Details
Wipe_method.png (26.89 KB, image/png)
2020-04-12 13:11 UTC, emohr 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description kvkv 2020-04-09 02:26:37 UTC 
Created attachment 127400 [details]
No Image file option  in Transitions - Wipe  19.12.3 for Windows

SUMMARY

No Image file option  in Transitions - Wipe

STEPS TO REPRODUCE
1. put two videos to separate tracks  
2. overlap them
3. Add Transitions - Wipe  in the top track

OBSERVED RESULT

No Image file option  in Transitions - Wipe

EXPECTED RESULT

Should have Image file option to select pgm file. 

SOFTWARE/OS VERSIONS
Windows: 10

KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 kvkv 2020-04-09 02:53:33 UTC 
Created attachment 127402 [details]
Wipe method no more options
Comment 2 kvkv 2020-04-09 02:57:08 UTC 
It only occurred when profile set to

Custom-> Vertical 720X1280 .
Comment 3 emohr 2020-04-12 13:11:35 UTC 
Created attachment 127468 [details]
Wipe_method.png

By clicking on wipe method I see the following:
Comment 4 Julius Künzel 2021-02-19 22:06:47 UTC 

*** This bug has been marked as a duplicate of bug 423619 ***