I had an idea for a clock skin but I've ran into two problems where I'm not sure how to solve or work around them. I'll just start with the first problem since the second one is a consequence of the first one once it has been resolved. Basically I made this minimalistic analogue clock with two images for the pointers. The analogue clock is only there because I like it from a design perspective but since I prefer a digital clock to actually read the time I'd like to add the digital time at the end of each pointer that changes according to their position (see the picture).
So from what I've seen I'd need to make a string to display the time and then rotate it at the end of the pointers of the analogue clock but is this even possible? At least I didn't find another example where this was used and from reading the documentation it doesn't seem possible just using Rainmeter since you can't combine two Meters Would I need a Lua script for that or am I just missing the obvious answer?
You do not have the required permissions to view the files attached to this post.
As a starting point you can do the following. It envolves just a little bit of trigonometry. The code is just the skin and not the complete structure in a rmskin.
ikarus1969 wrote: ↑January 29th, 2023, 5:44 pm
As a starting point you can do the following. It envolves just a little bit of trigonometry. The code is just the skin and not the complete structure in a rmskin.
Good solution, but there is a small thing which should be improved. I'd replace the MeasureTimeMinutes measure name in the Formula option of the [MeasureTimeMinutesAngle] measure by MeasureTimeMinutesDec:
The movement of the "digital minutes" improves with this trick.
And one more, however this is most probably addressed to Derenaya (the OP). why to use such a low Update? The Update of the original skin has been set to Update=50, which means 20 updates per second. In your code ikarus1969, this has been increased to Update=100 (10 updates per second), but even this is a little bit low. The default Update=1000 works well (at least if there isn't something I missed).
Thanks a lot ikarus1969 and balala that works (almost) flawless Just on small issue I've spotted. The minute number (obviously) moves on the X and Y-axis instead of a circle which, when staring at it, is pretty noticeable. Is there a way to improve / smooth this? You'd probably need it moving on an actual circular path I'd imagine
And one more, however this is most probably addressed to Derenaya (the OP). why to use such a low Update? The Update of the original skin has been set to Update=50, which means 20 updates per second. In your code ikarus1969, this has been increased to Update=100 (10 updates per second), but even this is a little bit low. The default Update=1000 works well (at least if there isn't something I missed).
Derenaya wrote: ↑January 29th, 2023, 7:28 pm
Just on small issue I've spotted. The minute number (obviously) moves on the X and Y-axis instead of a circle which, when staring at it, is pretty noticeable. Is there a way to improve / smooth this? You'd probably need it moving on an actual circular path I'd imagine
No, at least as far as I can tell, there is not too much to do about this. In fact ikarus1969's code moves the strings on a circle (by using the cosinus and sinus functions, they are in fact moving on a circle). However due to the fact that String meters can have only positions described by integers (so their X and Y values have to be integers), the position of the meter is changing in steps, causing the described issue. I don't see at the moment a solution for this.
Sorry, but maybe someone else will have a better idea...
Yep, but that skin has to have such a low Update, because its seconds pointer is moving continuously. There is nothing in your skin which could require lower update value than the default Update=1000. Recommend this, because this way you can reduce the load of CPU (even if for this code, it can't be too huge, even not with the original Update=50).
No, at least as far as I can tell, there is not too much to do about this. In fact ikarus1969's code moves the strings on a circle (by using the cosinus and sinus functions, they are in fact moving on a circle). However due to the fact that String meters can have only positions described by integers (so their X and Y values have to be integers), the position of the meter is changing in steps, causing the described issue. I don't see at the moment a solution for this.
Okay, no big deal as it's really not noticeable outside of staring at it.
Yep, but that skin has to have such a low Update, because its seconds pointer is moving continuously. There is nothing in your skin which could require lower update value than the default Update=1000. Recommend this, because this way you can reduce the load of CPU (even if for this code, it can't be too huge, even not with the original Update=50).
Yeah I changed it back
Also then for my second problem. Currently if the pointers are overlapping the numbers are in front of the pointers for which I was thinking of calculating when this will happen to then swap out the image of the minutes pointer with one that has a gap there as shown in the second picture. Figuring out at which times that will happen isn't that hard but I'm not sure how I'd then implement this or if that's even possible. I was also thinking about detecting overlapping pixels to trigger it but I doubt Rainmeter can do this.
Would I need a Lua script for that or am I just missing the obvious answer?
Just on small issue I've spotted. The minute number (obviously) moves on the X and Y-axis instead of a circle which, when staring at it, is pretty noticeable. Is there a way to improve / smooth this? You'd probably need it moving on an actual circular path I'd imagine 
