Hey sl23, thank you for bringing this to my attention. I can surely take it into consideration for this and future projects, as I understand how complex organizing multiple skin files can become.I've quite often needed a colour picker in general. There are so many apps, some good, some not so, some very bloated. I like the idea of this and how compact it is. It saves me having a dedicated app for something that doesn't get used a great deal but is there when needed.
One thing I would request, which may or may not be welcomed by yourself or others, is that I have now planned to install several utilities from the forums. But due to how people organise their skins, as discussed before, they become a mess when using a single @Resources folder. I have manually moved all components to a sub folder called #@#HSLidersSTA. My reasoning is that when you install several skins to be combined into a suite of utilities as I am currently doing, the resources folder becomes a complete jumbled mess due to poor organisation. Basically, everyone dumps their files straight into the @Resources folder making it difficult to dissect if you decide to remove or work on something that a user has added.
An example, let's say I add this skin, my skin launcher, my Segoe Fluent Font selector, and several of the top of the list utilities from the forum. Now if all of those were to be placed directly in a combined suite, they generally all just have random files placed directly within @Resources, how do you know which files belong to which skins? I suggested before and do so again here, requesting that you make a slight change and place all your files within a subfolder named after the skin.
For advanced users like yourself, the moderators and the dev's, they create their own stuff that they use. Most of us have to make do with what we find on here as we have little chance of creating something this complex. Which means we are left trying to organise a mess of files or having a ton of different Suites folders with one or two skins in to avoid turning the resources folder into a jumbled mess of random skin files. Fonts I have kept in the same place though.
Although the several others disagreed with my previous post, hopefully you will change this. Although I have personally changed it, I imagine many users don't know how to and rely solely on the Rainstaller to manage their installations. I dislike that as I don't know where things are being installed to. I like to know what's being put where.
Anyway, great skin, very much appreciated, thanks for sharing!
I would like to see not only the swatches, but the ability to load and save a palette of swatches.
Could you please share the skin with me to see exactly how you organized it? This would save me some time since I'm focusing on the next update for my Gauges.
I have my doubts about this since, according to the docs, the @Resources folder is ignored when scanning for skins, so using it to store resources improves the initial load time. But I'm open to try it out and see what happens. I think this HSLiders folder could very well be inside the @Resources folder anyway. Although I still have doubts about the fonts, since the docs say "fonts in the @Resources\Fonts folder are automatically loaded and can be used with the FontFace option in string meters." Which makes me wonder what happens with fonts that are not in this folder, do they have to be loaded manually? How?
And thank you, I'm glad you like HSLiders
Statistics: Posted by RicardoTM — Today, 8:31 pm