To have midnight at the top center, replace '90' in the StartAngle value calculation with '270'. The default starting point (Rad(0)) is at the 3 o'clock position, so just add (or subtract) the degrees to start where you want.
Nice edit on the skins!
Yes, I was never savvy at maths but once I learn something it tends to stick, mostly due to having a new "toy" to play with and the repetition of reuse while learning.
Whilst reading how the roundline works the zero degrees at 3 o'clock was something I picked up ok. Your putting it into focus got me where I wanted to be and 270 degrees was relatively easy seeing the correct math in action.
There are many ways to be different - there is only one way to be yourself - be amazing at it
The law of averages says what it means; even if you get everything right, you will get something wrong. Therefore; self managing error trapping initiates another set of averages - amongst the errors, some of them will not be errors, instead those instances will appear to be "luck". One cannot complain of the 'appearance' of 'infinite regress of causation', even if it does not have a predictable pattern, only that it requires luck to achieve.
The goal: Make a RoundLine Hour circle that starts at a variable time and concludes at another variable time.
What I think I need to do: Make a RoundLine Meter that has a "zero" position and it draws in an arc until the "end" position reletive to an actual clock's hours.
How to do it?: I can draw a circle, size it, position it, but not much after that.
I cannot seem to get my head around all of the different parameters - without a basic working meter to start from - basic would be managing the start and end positions effectively/accurately.
I will keep tacking away, and hopefully someone might be able to get me rolling in the right direction in the mean time.
There are many ways to be different - there is only one way to be yourself - be amazing at it
The law of averages says what it means; even if you get everything right, you will get something wrong. Therefore; self managing error trapping initiates another set of averages - amongst the errors, some of them will not be errors, instead those instances will appear to be "luck". One cannot complain of the 'appearance' of 'infinite regress of causation', even if it does not have a predictable pattern, only that it requires luck to achieve.
eclectic-tech wrote:So, if I understand, you want a 2 pixel wide, 20 pixel diameter radius circle, that shows when the sun is up/down in relation to your 24 Clock, which has midnight at the bottom center?
First you need to set the startangle at the offset to your 'zero' position (bottom center to match your 24 hour clock), so that would be (Rad(90)). Then add to that, the time of sunrise using the value of the sunrise hour times 15 (each hour of a 24 hour clock is 15 degrees) + the sunrise minutes times 0.25 (each minute is 1/4 of a degree) to set the starting point at sunrise.
Then in your measure to drive the roundline, use the difference between sunset hours times 60 plus the sunset minutes and the sunrise hours times 60 + the sunrise minutes, and divided that by the total minutes in a day (1440) to get a percentage.
You do not need to calculate the sundown, since it is the remaining percentage value of sunup.
So to display, use a roundline, solid filled circle, the same size as the sunup meter to start (this will represent the sun down time) and overlay the sunup roundline.
I used a 10 pixel wide arc to show the settings...
sundial1.pngThis will match the times on your 24 hour clock.
If you had something else in mind, let us know...
It has become a need that I figure out how to represent the sundown to sunup arc. However, I have been lost on the math.
Perhaps eclectic-tech has a suggestion?
There are many ways to be different - there is only one way to be yourself - be amazing at it
The law of averages says what it means; even if you get everything right, you will get something wrong. Therefore; self managing error trapping initiates another set of averages - amongst the errors, some of them will not be errors, instead those instances will appear to be "luck". One cannot complain of the 'appearance' of 'infinite regress of causation', even if it does not have a predictable pattern, only that it requires luck to achieve.
There are many ways to be different - there is only one way to be yourself - be amazing at it
The law of averages says what it means; even if you get everything right, you will get something wrong. Therefore; self managing error trapping initiates another set of averages - amongst the errors, some of them will not be errors, instead those instances will appear to be "luck". One cannot complain of the 'appearance' of 'infinite regress of causation', even if it does not have a predictable pattern, only that it requires luck to achieve.
You didn't include the variables file "@include=#@#RoundVariables.inc" so I checked your file assuming that file did not contain any useful info...
To eliminate the extra calculation errors, I modified the substitution of the SunriseAMPM and SunsetAMPM measures to substitute 0 or 12, instead of doing the multiplication math in the HourAdjust measures it simply adds the values. Also used the number value section variables in the StartAngle calculation (and modified your formula; you were adding a Rad value to a Rad value calc...).
You do not need to calculate the sun down time since it is always the remainder of the sun up time. So you can use a completely colored full 360 degree ring as the sun down time and overlay the sun up roundline meter to show the difference.
The sun down arc is what I was hoping to calculate, as that is what I am trying to achieve.
Having the sunup arc just eclipse a full circle is not the desired method in my case, as I am trying to have the appearance of a small gap between the arcs.
Is the sun down arc really weird to code? I have tried, but in vain.
Untitled.jpg
Is that possible, without insanity as i have come to know it?
You do not have the required permissions to view the files attached to this post.
There are many ways to be different - there is only one way to be yourself - be amazing at it
The law of averages says what it means; even if you get everything right, you will get something wrong. Therefore; self managing error trapping initiates another set of averages - amongst the errors, some of them will not be errors, instead those instances will appear to be "luck". One cannot complain of the 'appearance' of 'infinite regress of causation', even if it does not have a predictable pattern, only that it requires luck to achieve.
There are many ways to be different - there is only one way to be yourself - be amazing at it
The law of averages says what it means; even if you get everything right, you will get something wrong. Therefore; self managing error trapping initiates another set of averages - amongst the errors, some of them will not be errors, instead those instances will appear to be "luck". One cannot complain of the 'appearance' of 'infinite regress of causation', even if it does not have a predictable pattern, only that it requires luck to achieve.
eclectic-tech wrote:You didn't include the variables file "@include=#@#RoundVariables.inc" so I checked your file assuming that file did not contain any useful info...
It certainly is there, as the colors would not have been correct?
There are many ways to be different - there is only one way to be yourself - be amazing at it
The law of averages says what it means; even if you get everything right, you will get something wrong. Therefore; self managing error trapping initiates another set of averages - amongst the errors, some of them will not be errors, instead those instances will appear to be "luck". One cannot complain of the 'appearance' of 'infinite regress of causation', even if it does not have a predictable pattern, only that it requires luck to achieve.