zzag / plasma5-wallpapers-dynamic

Dynamic wallpaper plugin for KDE Plasma
329 stars 18 forks source link

Cannot read .heic files "/wallpaper.heic is not a dynamic wallpaper." #43

Closed gcarlos64 closed 4 years ago

gcarlos64 commented 4 years ago

After de 3.0 release, that includes HEIF format for the dynamic wallpapers, I can't set any .heic wallpaper for my desktop, cause it isn't recognized as a dynamic wallpaper. I'm using Archlinux with the KDE desktop environment. Thanks in advance!

BruceZhang1993 commented 4 years ago

Same here. KDE on Arch Linux.

-- Update: I tried to create heic file by kdynamicwallpaperbuilder tool and it worked pefectly.

zzag commented 4 years ago

Did you use the kdynamicwallpaperbuilder tool to create that wallpaper.heic file?

Shatur commented 4 years ago

Same here, but I downloaded .heic files from dynamicwallpaper.club. For example, this wallpaper not works, only shows preview.

zzag commented 4 years ago

Dynamic wallpapers for macOS and this plugin are incompatible. However, it's possible to write a (Python) script that populates a heic file with metadata that is necessary for this plugin to function as desired. See src/lib/metadata.xml and src/lib/kdynamicwallpapermetadata.cpp for more details.

Dkoeddnsnp commented 4 years ago

I would be convenient to have 100% compatibility of this plugin and macos version.

gcarlos64 commented 4 years ago

Dynamic wallpapers for macOS and this plugin are incompatible. However, it's possible to write a (Python) script that populates a heic file with metadata that is necessary for this plugin to function as desired. See src/lib/metadata.xml and src/lib/kdynamicwallpapermetadata.cpp for more details.

Now I understand! Thank's for the explanation.

zzag commented 4 years ago

See https://github.com/zzag/plasma5-wallpapers-dynamic/commit/7c1150c257a63fd1afee3f51c88397952702155b

Shatur commented 4 years ago

Thank you a lot, the solution worked perfectly. But is there any sense to use .heic if it does not compatible with MacOS format? Maybe use another format name to avoid confusing? In previous versions, the .json format was quite convenient.