@Jorge,

I know you are finalizing the BETA and it may be too late until next one. If you have not and can PLEASE allow for icon changes that would be great.

Thank you for the naming conventions in mail, I appreciate it.
Just the the two drive meters and I can do the entire icons. I only have to edit the red graph to dark blue and it is done in drive image below.

here is ice palace using the preferences. Thanks for all of your information assistance.

@Jorge - minor bug

I tested the loading of an icon you suggested to me and that part works great. As I knew, that then becomes the default unless I click 'Default' again'.
What seems to happen randomly, is after clicking default, every so often the icon I loaded comes back and is not storing the default settings?
I did another and this one while great for the theme it belongs in, not so much for other themes.
Yes I have started creating icons for all of them. Yes I understand it is purely good for testing and is a global setting not a theme setting. The issue is clicking default doesn't seem to restore as well as expected?
I hope I made sense?

Steps to reproduce?

Hello Jorge,
Currently, I'm not working on themes anymore, but I've been following the forum's progress on the Disk Meter module, and I must say you've done excellent work. I haven't participated since August, no replied to your November post, simply because I knew you were working hard on the Betas and the Disk Meter module...
I had no opinion on the Disk Meter module or how you intended to implement it.
Even though I can sometimes be a bit harsh in my posts, it's not intentional; it's part of the game on a forum. That doesn't change the fact that I have the deepest respect for you and your work.

I downloaded the "iStat Disk Meter" file and looked at the iStat.wsd file. It's the most complex theme file I've had to work with, but with patience, it's manageable.

One question: when you change your disk icon (personal icon), the disk letter appears automatically (C, D, E...). Couldn't this be removed to avoid duplication, as shown in the screenshot I provided.
In the .wsd file I configured: For the disk letter
DiskEnabled01H=True
DiskFont01H=Arial
DiskFontSize01H=12
DiskFontBold01H=True
DiskFontItalic01H=False
DiskFontColor01H=16777215
DiskEffect01H=0
DiskEffectColor01H=0
DiskXPos01H=48
DiskYPos01H=2
DiskMaxWidth01H=47
DiskPos01H=1
DiskPrefix01H=
DiskSuffix01H=
DiskTicker01H=False
This configuration caused a duplicate disk letter...
Could we remove the disk letter on the icon..?
Also, to prevent the shadow from flipping to the left when switching from horizontal to vertical, I created two skins (WsDisk.png and WsDiskV.png).

Another thing, apparently the overlay isn't stretching correctly; I had to create two specific overlays (H and V) for my four discs and two skins.
Believe me, I'm very laid-back and I also value peace, but what more can I say than a forum is a forum...
Sincerely and with all due respect...
Picco14.

Has to be a quick answer for now, sorry. Currently, at least, there is no way to replace the disk letter... However, I think I can add a last minute addition of preventing the disk letter from appearing in the icon if the user has it enabled in the disk meter theme.

Another alternative is not to use an icon at all... and this is just an idea: you can use, for instance, a multi-state graph (DiskShowMulti) with at least 10 frames (each frame would be 10% of disk space used). This would give you complete freedom on what to display...

At least I think it would work, don't have the time right now to look into it, only after new year.

Happy New Year!

Thanks Jorge for your reply...
I tried with DiskBarEnabled01H=True and DiskBarEnabled01V=True, it wasn't very successful, but that's okay considering all the work you've done...

Happy New Year 2026 to you and all your loved ones as well.
Happy New Year everyone...

Sorry did n.ot think things through. Graohs are tied to bytes read and writtwn, but i can make only the histogram and the othes tied to used space. Tha woul wirk.

Not having an AVC, dont worry, just have a 2 year old sticking a finger in my mouth and nose. Explain better later

Ok, sorry guys, had to wait for Noah to fall asleep. He kept putting his little finger up my nose and in my mouth and laughing his head off while I was trying to type on my phone.

So, it was the right idea but the implementation is not there yet. This is going to delay the official release of v25.12, but ah well...

You have four types of graphics you can use on a module (and you can use them all at the same time if you want): histogram (DiskGraphEnabled), bar graph (DiskBarEnabled), gauge (DiskShowGauge) and multi-image (DiskShowMulti).

Normally these are ALL tied to the SAME value (for instance, net bytes in, or % of cpu usage). However, the disk meter is special and it doesn't HAVE TO be this way.

This said, all the disk meter graphs are indeed currently tied to the same value (DiskGraphEnabled01 for bytes read/s, DiskGraphEnabled02 for Bytes Written/s). For some reason I thought the non-histogram graphs were tied to the used disk space %. They aren't. But they can be made to.

So, there are two ways to deal with this: either only the histogram is tied to bytes read/written per second and all the other graphs are tied to % disk used space (not sure this is a good idea as skinners might want to use the other graphs for that too) OR I allow the skinner to select which value a particular graph is tied to for the disk meter (e.g. 0 - bytes read/written per sec, 1 - disk used percentage).

If you guys have any other ideas now is the time to speak up. Anyway, this would allow disk meters like this (instead of using the icon, you use a multi-image graph, for instance)

Ok, I changed the code so that if the drive letter text is enabled (DiskEnabled01H/DiskEnabled01V), the icon does not display the drive letter.

I DID MAKE ONE OTHER CRUCIAL CHANGE THOUGH, I removed the automatic ":" in front of the drive letter text option for DiskEnabled01, so that now only C is displayed instead of C:. You need to add the ":" as a suffix; i.e. DiskSuffix01H=:

Also, if you want to add a margin between the the end of the disk section and the right edge of the container bitmap increase the value of DiskSectionPadRightH, DiskSectionPadRightV

That looks really good and more appealing, but that's only my opinion.

Looking at everything in the file and trying different combinations, it seems the ability to extend the bitmap canvas is not possible without using padding in the file and limited to that, but it would be nice if images could be place L,R,T&B via canvas resizing rather than padding. In the other modules resizing the bitmap canvas only involves shifting the image inside the canvas. In this it takes over the entire canvas no matter what size it is and I tried a LOT of different sizes as well as a LOT of padding variations.
Being able to specify an exact placeholder size for the disk modules H&V would be useful that doesn't take over every resizing option. I get it needs to expand for 26 drives etc but that's not the point.

As an example - If the disk module is Horizontal then anything on the top, bottom or left is unaffected by a canvas size resize. So if if is 250 pixels high, it would expand in width.. any canvas if the skinner wanted to put an image above and create the canvas 400 pixels high would not affect the disk module and the disk module would leave 150 pixels above that it won't touch. have to ask, even if it is not possible.

Actually thinking about it better there are three ways, and the third way is the best and works fine without having to modify hardly any code or create "special cases". Add one more graph block, but this one dedicated to % disk usage. So, graph block 0 is bytes read/sec, graph block 1 is bytes written/sec and graph block 2 is used space %,

Makes sense?

Of course, showing a histogram for used space % makes no practical sense since this value hardly changes over time, but this allows the skinner to use all the other three graphic options (bar, gauge or multi-image) without this conflicting with the bytes read/written graphs.



This module is not like all the other modules, and all you need to do is shift the way you are thinking... forget about extending the bitmap canvas, instead use the tile and padding values to control where everything goes (or use a combination of both).

Remember: start of first section in the canvas = lTile + lPad. End of last section = bitmap width - RTile - RPad. You want a wider right margin (i.e. space between the end of the last section and the edge of the bitmap/canvas)? Increase RPad (e.g. from -10 to +32 pixels). Negative values for LPad, RPad, TPad and BPad are only used when you want to make the sections extend into the tile areas, otherwise use positive values.

Not sure why this is causing so much confusion?

And I was wrong, tried it did not go as well as I thought it would. Back to the "mode" idea for the other graphs.

I did actually try this. Keep in mind the way the module is made, I found the number of drives affect the size and shape of the image added into the module in the padded spaces. You have blocks justifiably assigned for each drive which makes sense. However, If I pad to the right and I have tried several ways... I test on a machine that has 4 drives and many people will have at least two drives and an external, so it is good for that.

THEN - I put it on my DAW machine with 10 drives or laptop with only one, and the image looks like it is reflecting from a coney Island mirror - It either becomes skinny or pudgy. I can see how I can manipulate everything else but not having any joy with the padding. I'll revisit it later.

I am loving the hues in the drive module. I have a better grasp on that than the Hex conversions with colors in the other modules. The text is easy enough as it it is either H or V.
I'll get it.

Jorge I won't go here again until I am sure I have exhausted every possibility, and if I do, I will supply images to demonstrate.. Cheers

@Jorge

- No big deal but noticeable - I am sure it is by design, but I notice the ring chart with colors is far more capable of getting naturally bright colors than the disk drive and I'm pretty sure anyone else who has played with it noticed it too. To get close to a similar brightness with the disk drive, luminescence only tends to make it more pastel. Yes I maxed saturation to be sure, and it is different and less capable of naturally brighter colors. It's a lot easier to get the same near identical dark colors if the natural colors are bright by decreasing saturation and luminescence.
In case you do not believe me, try and get a RED 255 or a light cyan without losing all of the detail on the disk drive.

So yes, I think being able to skin our own drive icons for matching themes will be a big + if this is intended.
A

P.S

An ability to choose the default display (Icon/Full and Vert/Horiz if full) because the user can choose icon or full meter anyway from the right-click menu would be good in the configuration file. This way the skinner can display as intended without affecting the user if the user prefers something different.