Yep, forgot to suppress spaces, but as always, I used quotes so it alleviated the (potential) issue. And you're right, I never use spaces in measure, meter or group names either (if needed, I use _ instead), but this time I went on doing that out of a lack of focus and to better emphasize that the OP should replace the text with its actual group name.
It is currently September 21st, 2024, 3:18 am
autodetecting disks - if disk exist then add to skin... is this possible?
-
- Rainmeter Sage
- Posts: 8195
- Joined: February 27th, 2015, 2:38 pm
- Location: Terra Yincognita
Re: autodetecting disks - if disk exist then add to skin... is this possible?
-
- Posts: 14
- Joined: February 6th, 2020, 4:11 pm
Re: autodetecting disks - if disk exist then add to skin... is this possible?
the second solution is definitely the way to go for us... i dont think we need extra skins per disk.balala wrote: ↑February 7th, 2020, 3:06 pm There seems to be a great confusion on Rainmeter terminology. According to the first quotation, you've created a new skin for the third disk, but according to the second one, only new meters have been created. The described method works in either case, just that in first case you have to hide the whole skin, while in second one, just the appropriate meters (or as Yincognito suggested the appropriate group of meters).
So in first case:In second case on the other hand:Code: Select all
[MeasureTotalDiskSpace1] ... IfCondition=MeasureTotalDiskSpace1=0 IfTrueAction=[!HideFade] IfFalseAction=[!ShowFade]
Which solution works, depends on how is (are) those skin(s) created. If you have a distinct skin for each disk, you have to use the first method, however if there is only one single skin, containing the meters for each disk, the second one is good for you.Code: Select all
[MeasureTotalDiskSpace1] ... IfCondition=MeasureTotalDiskSpace1=0 IfTrueAction=[!HideMeter meterLabelDisk1][!HideMeter meterValueDisk1][!HideMeter meterBarDisk1] IfFalseAction=[!ShowMeter meterLabelDisk1][!ShowMeter meterValueDisk1][!ShowMeter meterBarDisk1]
Rereading the previous posts I believe the second case is alright, however I'm not entirely sure.
i feel its easier to keep them all in one skin.
thanks for all your help... starting to get the hang of this
i have another issue but ill start a new thread....
cheers!
-
- Rainmeter Sage
- Posts: 16568
- Joined: October 11th, 2010, 6:27 pm
- Location: Gheorgheni, Romania
Re: autodetecting disks - if disk exist then add to skin... is this possible?
Agree. But not this is what I understood from your initial post:RogerDingo wrote: ↑February 7th, 2020, 3:33 pm the second solution is definitely the way to go for us... i dont think we need extra skins per disk.
i feel its easier to keep them all in one skin.
That's why I have added my reply.RogerDingo wrote: ↑February 7th, 2020, 12:12 pm i added a 3rd disk to the server and the only way to add a new meter was to modify 2 Disk.ini and create a new ini file.. called...
3 Disk.ini
-
- Rainmeter Sage
- Posts: 16568
- Joined: October 11th, 2010, 6:27 pm
- Location: Gheorgheni, Romania
Re: autodetecting disks - if disk exist then add to skin... is this possible?
As said, all those (meter and measure names, variables, groups and so on) let you to use spaces. Not as if it's not allowed, it's just not a good habbit in my opinion.Yincognito wrote: ↑February 7th, 2020, 3:21 pm Yep, forgot to suppress spaces, but as always, I used quotes so it alleviated the (potential) issue. And you're right, I never use spaces in measure, meter or group names either (if needed, I use _ instead), but this time I went on doing that out of a lack of focus and to better emphasize that the OP should replace the text with its actual group name.