[CDriveMeterDiskFree] and [CDriveMeterDiskInfo] are the two string that I want to show on my container. (the gray bar) I'm making them slide up and down when the mouse is over the container.
Since the two meter are not and will not be always of the same wide, I'm using the Calc with a max(,) formula to get the wider meter wide.
But the formula at the start is returning me 105 instead of the 140 which is the max between value the both.
Resulting in the container being smaller at start and for whatever reason the Calc then return the right value of 140 which result in the right size of the container.
I don't get it why the Calc is returning me a false value at first for then after returning me the right one without any change of the both meter wide in betweem.
Thanks that seem to do the trick !
Tho adding a OnRefreshAction=[!Update] on [Rainmeter] would that risk adding more work on the processor if the skin as a lot of meters and measure ?
Duschmoll wrote: ↑September 2nd, 2021, 4:00 am
Thanks that seem to do the trick !
Tho adding a OnRefreshAction=[!Update] on [Rainmeter] would that risk adding more work on the processor if the skin as a lot of meters and measure ?
It's a one time process, so it would hardly matter. Still, the second way is preferable if it works.
death.crafter wrote: ↑September 2nd, 2021, 5:09 am
It's a one time process, so it would hardly matter. Still, the second way is preferable if it works.
Thanks for the info, sadly the second method doesn't seem to work.
I think it's because the Calc is puting an oupout of 105 at first, I don't understand where this number come from.
To put it simply the
[CDriveContainerWide]
Measure=Calc
DynamicVariables=1
Formula=Max([CDriveMeterDiskFree:W], [CDriveMeterDiskInfo:W])
is the equivalent of this =>
[CDriveContainerWide]
Measure=Calc
DynamicVariables=1
Formula=Max([140], [131])
The outpout of [CDriveContainerWide] is 105 then after an update is 140.
So where is this 105 coming from ?
For the purpose of this test, both 140 and 131 are the same from the begining, you can see that in the gif.
Use death.crafter's OnRefreshAction to solve the display issue.
The 105 happens because when first run, the value for your disk measures are zero, so the only width the formula sees is the text in those meters; Text="- %1B / %2B" and Text="%1B / %2B". Those characters provide the 105 width you initially see until the measures populate the actual drive values.
Adding OnRefreshAction=[!Update] in the [Rainmeter] section will update the meters once the skin is loaded and the measures have values.
This will not add any load to your computer as it only happens once when the skin is loaded. Your UpdateDivider on the drive measures is what will control any system load.
In the end OnChangeAction=[!UpdateMeter ] was what I needed.
I can't use OnRefreshAction=[!Update] because I'm using the same principal for the wide of text showing the Mhz of my CPU. So the value is constantly changing and the meter need to be updated when the value is changed.
Cheers for the help, without you I wouldn't have been able to do it !
Sorry for my bad explaining of the situation, my english is not the best