WACUP
General => Skins => Topic started by: ariszlo on May 23, 2023, 08:58:43 AM
-
The previous version (https://getwacup.com/community/index.php?topic=1175) of Quinto was broken through and through in WACUP unless you kept a copy of its scripts folder in C:\Program Files (x86)\Winamp\Skins\Quinto Black CT v3.6. You no longer need to do so.
Quinto Black CT v3.7.exe, Quinto's installer still will not install the skin into WACUP's skins directory. You still need a file with the name winamp.exe in C:\Program Files (x86)\Winamp to make the installer believe you have Winamp on your machine. (The file does not really need to be a real exe file, a plain text file with an exe extension will do as well.)
Once Quinto is installed into Winamp's skins directory, you can move Quinto's folder into WACUP. And that's it.
Get Quinto Black CT v3.7 here (https://forums.winamp.com/forum/skinning-and-design/modern-skins/4615995-quinto-black-ct-v3-7#post4616979).
Explanation
Version 3.6 of Quinto hard-coded Quinto's path in its makis but now it uses @SKINPATH@ instead.
-
Does it still have the requirement to wipe the studio.xnf file at the cost of losing customisations for all other modern skins ?
-dro
-
Yes, it still does.
-
Yes, it still does.
I like Quinto Black, but this is a major stumbling point. PeterK needs to have the installer remove all Quinto related stuff from studio.xnf instead of requiring a new studio.xnf for each version upgrade.
-
I doubt he would & it's likely too much hassle to try to do it especially from an installer or without a custom tool to do it. At least the installer doesn't seem like it's doing it (not tried so might be wrong on that assumption).
I still don't get why it's a requirement since if it's due to config changes within the quinto skin then just using different names for the config attributes would suffice without the brute force option that messes up all other skins which I suspect is more down to not being bothered about anyone not using the quinto skin (not that it's great for anyone who might've been using prior quinto skin installs either).
-dro
-
I dropped PeterK a note and he said it is not possible for him to have the Quinto Black CT installer clean up the studio.xnf file. He also explained that using new names for stuff would not prevent old entries from causing errors in new versions, without a complete rewrite of the skin.
In my case, I've gotten pretty good at replacing entries for my other skins, but there is always the chance of errors that cause me to skip new Quinto versions unless really interesting features are added. After-all, from the ui control side of things, WACUP provides alternate ways to control everything that Quinto provides controls for.
PeterK will soon be releasing v3.8 that will have compelling new features, imo.