I have been doing quite well on my own so far, but have reached a certain dificulty lately:
My intent is to determine the lowest (and, separately, the highest) value out of a wide range of values, while making use of the following calculation formula:
Nevertheless - and until now the only obsacle I was not able to overcome on my own - it does not work.
The error-message presented by rainmeter reports the following: Error - [time-code] - The meter [15DayForecastLowestTemp] cannot be bound with [CalcLowestTemp]
Error - [time-code] - Calc: Unmatched brackets in [CalcLowestTemp]
As I mentioned, I was trying to solve this on my own. Besides that I was also investigating before making this request for help for quite a while; with no results of any productive aid to this particular problem.
You have an extra ")" on your inner most pair.
Basically, this: (Day13TempLow <= Day14TempLow ? Day14TempLow[b])[/b] : Day13TempLow)
Should be this: (Day13TempLow <= Day14TempLow ? Day14TempLow : Day13TempLow).
Having said that, I am not sure if this many conditional statements will work, I believe there is a limit of 9, but I might be wrong.
It appears that I have committed a mistake not just in the spelling of the formula but also in the syntax.
Apparently this formula only displays the lowest value that come right after Day0 not comparing it further with the subsequent values, leaving those out of the extraction-progress to determine the lowest value out of the entire range of values (value-count: 15).
I am reaching my math-skills here - I am rather a language/grammer junkie than a math-talent.
Should I, prehaps, rather workout a formula using and / or? - but than I dont see how I will draw the final conclusion: extracting the lowest value out of 15 different values.
I hope for more suggestions, you have helped me very much until now. In science and failure is as much a success as a real success - we, so, learn more for the next intent.
I will continue to work on this myself, even-though I believe there are more qualified people in this community who will handle such a problem with ease, while other (me) must squeeze the bits and peaces out of their brain's grey-matter. Therefore, if there won't be any suggestions, I will post my result, in order to help other's who might want to solve a similar problem - if ever I conclude in a result. :P
Yes, Lua is one good way to do this. Here is a little sample of how one might attack this problem:
Here is the skin. I just used some Calc measures to gin up some random numbers between 0 and 100 every 5 seconds, to use as the values we want to find the least of. I don't have your full skin, so I assume you are getting the values from some weather skin or SpeedFan skin returning temperatures, You should be able to use this approach with what you are doing.
If you look, the key here is how you name the measures. Just name them all the same, tacking a number from 1 to whatever on the end. Note: If at all possible, use numbers from "1" to xxx, not "0" to xxx, as Lua is much happier with tables that are indexed starting with 1 and not 0.
So what this does is get the 8 values into measures, then call the Lua script. As you can see, I am telling the Lua script how many measures there are with MeasureCount=8, so it knows how many to get the values for.
Then there is a reasonably simple Lua script. I called mine Test.Lua in the same folder with the skin:
PROPERTIES =
{
MeasureCount = "";
}
function Initialize()
iCount = tonumber(PROPERTIES.MeasureCount)
tMeasures = {}
for inc = 1, iCount do
tMeasures[inc] = SKIN:GetMeasure('MeasureTemp'..inc)
end
end -->Initialize
function Update()
local tValues = {}
for inc = 1, iCount do
tValues[inc] = tMeasures[inc]:GetValue()
end
table.sort(tValues)
return tValues[1]
end -->Update
What it does is get the number of measures to check using that "MeasureCount" setting, then build a table "tMeasures" that has the handles to the 8 measures in the skin.
Then on each update of the script in the skin, it creates another table "tValues" that holds the current value of each measure.
Then it simply sorts the table tValues, so the lowest number will be in index "1".
Then it returns that value of tValues[1] to the skin, to use in your meter.
Note: You could easily return the "highest" number instead, by using return tValues[iCount].
Caution: If you are using WebParser measures to return the values, the measures will return strings instead of real numbers. (even if they look like numbers) You can address that by using tValues[inc] = tMeasures[inc]:GetStringValue() instead of tValues[inc] = tMeasures[inc]:GetValue() in the Lua.
Let me know if you have any questions about why / how this works, or if you have trouble fitting the idea into your skin.
just as much as all of you, fellow designers, who have responded to my calling... you are so very much out of my league, I can not even commence to comprehend how much I still have to learn about this subject. I have been developping several skins since I have recently begun skinning, but seldomly reached my limits (as afforementioned). And now I am to discover that there is an entire new, as of yet - to me, undiscovered section of scripting within rainmeter.
I am most certainly confused with your product, but see (after running your scripts) where it leads to.
Furthermore, I realize that my request hindered you from being able of constructing just what I was searching for - due to my vagueness. Please accept my appologies for thus - I will be rather specific now:
I intent to script a weather app that returns Temperatures (the high and low for each day) for 15days to come, using the WebParser-Plugin (as you had guessed, jsmorley). Unlike the script you produced, I wish to return the tempreatures merely once per actual (skin-)update, not in a consecutive changing (and random) pattern. The information exracted by the WebParser is constant. (Again: I wish to appologize for the wasted time.)
Once you run it you will notice that this idea of mine has just recently begun - it is rather undevelopped.
As commonly known, images expess more than a thousand words:
I attached an image of the result how I imagine it to be.
Regarding the image:
As you notice, I do not just wish to determine the lowest and hightest temperature within the range of the 15 days of forecast temp. values to limit the lines/graphs parameter - but I wish also to display the information in two graphs (each dot for its appointed day, in its corresponding height on the temperature scale, in proportional relation to the other values and all within the margin that has been determined by the affore-calculated lowest and highest temperatures).
I hope that was not too mixed up and uncomprehendible - people keep telling me to write shorter sentenses :P.
Again: Thank you so much!
I would like to mention your name (and the one's of the other productive supportes) in my project once I have finished it. I will then also present it here of cause.
Methyer
You do not have the required permissions to view the files attached to this post.
Much bigger project than I can dig into, but if you run into something where you have a specific question about how to do something in Rainmeter, feel free to ask.
