Re: Playlist-Manager-SMP
Reply #252 – 2023-05-26 19:51:41
Read this:https://github.com/regorxxx/Playlist-Tools-SMP/wiki/Wine There are users who are more capable on that topic than me though. But maybe that helps. If there is additional feedback, I will update all wikis and readmes as needed. (also check the readme PDF) The suggestions from the wiki didn't help unfortunately. Also the link to the SMP Wine page is dead. Maybe this should be linked instead: https://theqwertiest.github.io/foo_spider_monkey_panel/docs/faq/wine/ The only thing that worked in the end was manually adding the following registry entries:[HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Fonts] "Segoe UI (TrueType)"="C:\\windows\\Fonts\\segoeui.ttf" [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT\CurrentVersion\Fonts] "Segoe UI (TrueType)"="C:\\windows\\Fonts\\segoeui.ttf" Of course the paths need to point to a file that actually exists. In a standard wine prefix, these files don't exist, so they'll have to be added manually. Alternatively, one could use a wine-readable path to any other font file on the system, of course.Try to put the font in the user directory "/home/user/.local/share/fonts". Create one if not there and rebuild font cache "fc-cache -f -v" You can also use "/usr/share/fonts" if you want to make it available for all users. Adding the file isn't enough, there needs to be a registry entry.- A way to order playlists manually, using an index property or such. Even if this seems trivial, it's not due to supporting physical playlist files. Adding an index tag at the playlist would mean having to rewrite them all whenever a playlist is added, removed or order changed. Have in mind my manager works like the foobar album manager. You can not manually sort that. I may add an additional layer to store those indexes outside the actual playlists files; but in such case order would be limited to your individual installation (can not move the playlist to other instance and preserver the order). Yeah, that did cross my mind. An external file would probably be the best solution. Perhaps it would be helpful to add a unique ID to each playlist file which can be referenced by the index file, so it doesn't depend on filenames. The "By date" sorting scheme is based on the modified date. For some purposes, creation date would make more sense. That one is trivial to implement, just done it in 5 min. I will also look into implementing it for UI-only playlists, storing the date internally. Awesome.