Very new to this so not sure if i have missed something
I have created a Rainmeter SKin that has one measure(This runs a powershell script and uses returned values) and one meter(Source to follow), it works fine but the problem i get is it never refreshes.
So it works when i manually refresh but i would like it to run/update every 5 mins.
The second question would be how to split the returned data from powershell.
Currently it returns a value that is three lines and Rainmeter treats them as one value, how would i split these up and create three different Meter's from it?
Alrighty i have improved this better by using a Webparser.
Only problem i have now is that the Hashrate only updates after the first update.
So if i click refresh it is set to 0,00 and if i wait for the update interval it then refreshes with the value.
Please note the Dynamic Variable Snippets i slapped in to try get it working may not be needed.
Swiftzn wrote:Only problem i have now is that the Hashrate only updates after the first update.
So if i click refresh it is set to 0,00 and if i wait for the update interval it then refreshes with the value.
Not knowing the value of the RxAddress variable, we can't get the [MeasureGetStats] measure to work. Please post a possible value for the needed variable.
Furtherly, I'm not sure, are still interested into your first question?
In your case, your RunCommand measure MeasureGetStats is triggered with OnRefreshAction. This means that RunCommand measure will only be run once when the skin is loaded and/or refreshed.
In your case, your RunCommand measure MeasureGetStats is triggered with OnRefreshAction. This means that RunCommand measure will only be run once when the skin is loaded and/or refreshed.
Swiftzn wrote:Only problem i have now is that the Hashrate only updates after the first update.
This is caused by the UpdateDivider=120 option, added to each child WebParser measure. Remove them.
On the other hand, I have a remark.
On the parent WebParser measures (in this case [MeasureGetStats] and [MeasureGetBalance]) usually we don't use UpdateDivider options. It's not a too big mistake, it can be used even there, but usually instead we're using the UpdateRate option. Details here: https://docs.rainmeter.net/tips/update-guide/
In the meantime, you got the reply about your first question, from Brian and jsmorley, so, I don't post mine too.
Thanks for all the replies. learnt a lot already
Thanks balala, their responses do infact answer my original question, though i have switched the run command for a webparser so no longer needed,
i will be removing the UpdateDivider from the child ones and looking into the UpdateRate
Thanks for all the help so far guys
First skin so still learning haha.
***EDIT***
And now it works perfectly thanks you all.
This can turn out to be very useful for reporting and monitoring haha
I'm glad if I helped.
Just one more: the !CommandMeasure bang can still be used on the WebParser measures, but in a bit different form. You don't have to Run the parent WebParser measure, but to Update it. So the [!CommandMeasure MeasureGetStats "[color=#FF0000]Run[/color]"] bang would be [!CommandMeasure MeasureGetStats "[color=#00FF00]Update[/color]"]. Not needed usually, but if you want to manually update the WebParser measure (trough a click, for example), this is how you have to do it. Just be careful to use under the !CommandMeasure, the parent WebParser measure, not a child one. If you don't use UpdateDivider on the child measure, they will by updated immediately after the parent measure.
Swiftzn wrote:First skin so still learning haha.
Go ahead and feel free to come back with any question, if you have any.
balala wrote:I'm glad if I helped.
Just one more: the !CommandMeasure bang can still be used on the WebParser measures, but in a bit different form. You don't have to Run the parent WebParser measure, but to Update it. So the [!CommandMeasure MeasureGetStats "[color=#FF0000]Run[/color]"] bang would be [!CommandMeasure MeasureGetStats "[color=#00FF00]Update[/color]"]. Not needed usually, but if you want to manually update the WebParser measure (trough a click, for example), this is how you have to do it. Just be careful to use under the !CommandMeasure, the parent WebParser measure, not a child one. If you don't use UpdateDivider on the child measure, they will by updated immediately after the parent measure.
Go ahead and feel free to come back with any question, if you have any.
To be clear, child measures have their value set "by" the parent measure when it executes, not "after". They are updated normally as well, for purposes of executing IfCondition or OnChangeAction options and such on them, but their value is not set by the measure update process. It is set by the parent measure itself. It's why in 99.9% of cases, UpdateDivider makes no sense on a WebParser child measure.