Zdravo @selezli, pitam se da li je moguće napraviti “SFVIPplayer” svjestan direktorija “portable_config”postavljen pored “sfvip player.exe”, gde bi sve MPV povezane konfiguracije trebale ići (“fonts”, “script-opts”, “scripts”, “shaders”, “mpv.conf”, “profiles.conf”, “input.conf”). Tačno onako kako je poželjno u "MPV specifikaciji" za prenosne podešavanja na Windows. Jedan od razloga jeste da se Windows deluje vrlo neprijateljski raspoloženje za skripte, što je omotač za “$MPV_HOME” slomljen. Takođe premeštaju te skripte i konfiguracione datoteke u tom standardnom imeniku za prenosivost će olakšati modifikacije i uložiti će glavnu direktorijum. Naravno, “lib” direktorij, "libmpv.dll", "libthemes.dll", “yt-dlp.exe”, “Updater.exe” i bilo šta povezano sa zadanom funkcionalnost “SFVIP Player” ostali bi tačno gde prvobitno je postavljeno. Ova promena je samo za poboljšanje i konfiguracione promene MPV-a.
Orig. English
Hi
@salezli, I wonder if it is possible to make “SFVIPplayer” aware of the “portable_config” directory placed next to “sfvip player.exe”, where all mpv related configurations should go (“fonts”, “script-opts”, “scripts”, “shaders”, “mpv.conf”, “profiles.conf”, “input.conf”). Exactly as it is preferred in the “mpv specification” for portable setups on Windows. One of the reasons for it is, that Windows acts very unfriendly towards scripts, which makes the “$MPV_HOME” wrapper broken. Also moving those scripting and configuration files in that standard directory for portability will make modifications easier and will unclutter the main directory. Of course, the “lib” directory, “libmpv.dll”, “libthemes.dll”, “yt-dlp.exe”, “Updater.exe” and anything related to the default functionality of “SFVIP Player” would stay exactly where it was originally placed. This change is only for mpv related enhancement and configuration changes.