Mor3bane wrote: ↑May 12th, 2020, 12:13 pmI am curious but am wary of the talk about high cpu usages. My system is running high anyway so, the gif would alleviate my curiosities.
Yeah, the talk about high CPU usage was regarding the OP's original code / skin, and not about his edited version (still high for my taste, but at least not 98%, LOL) or my code (which had nothing to do with his skin, it was just a simple sample I tweaked to illustrate the behavior of a container meter in relation to TransformationMatrix).
As for me, you can't imagine how "wary" I am about the CPU usage, LMAO. Just now I was thinking whether or not to still continue developing an audio skin addition to my suite ... just because of a 1% to 3% increase in CPU usage caused by 2 simple AudioLevel measures updating every second. So you can be sure my code is "safe" from that point of view - there is no one more efficiency oriented than me on this topic.
eclectic-tech wrote: ↑May 12th, 2020, 4:03 pm
Here is a GIF showing the original code action, then adding the 'Container', and refreshing...{Click image to animate}container1.gif
Sorry, but that wasnt what I meant. I gathered there was some kind of animation? Perhaps that in an animated gif?
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.
Mor3bane wrote: ↑May 12th, 2020, 10:19 pm
Sorry, but that wasnt what I meant. I gathered there was some kind of animation? Perhaps that in an animated gif?
Mor3bane wrote: ↑May 12th, 2020, 10:19 pm
Sorry, but that wasnt what I meant. I gathered there was some kind of animation? Perhaps that in an animated gif?
After posting, I figured this was not what you wanted...
Sorry, but I am not going anywhere near this skin package, as it is not at all interesting for me
Perhaps Mithyr Sar or Yingonito can post an animation...
eclectic-tech wrote: ↑May 13th, 2020, 12:20 am
After posting, I figured this was not what you wanted...
Sorry, but I am not going anywhere near this skin package, as it is not at all interesting for me
Perhaps Mithyr Sar or Yingonito can post an animation...
Yeah, well, I tried scaling it down and increasing the angle increment through the skin's own variables, but at 30% to 45% CPU usage for a 235x235 resized image (!!!) my non-failing MSI AB couldn't even capture all the frames, so I ended with invalid frames in the video that VirtualDub2 couldn't obviously encode, LOL.
But if Mor3bane wants to know what it is, it's just the circle shape in the screenshot I posted (bar my dotted yellowish "measurement skin" on top of it) rotating at a customizable angle increment / size / position / etc., done with TransformationMatrix from Lua (I have no idea why the OP used Lua for this, as it could have been done just as well from Rainmeter itself). The OP's main mistake with this, as I mentioned earlier, was using images (big ones) to do this, when for this scenario a Shape meter equivalent would have been way more easier and friendlier on the CPU.
eclectic-tech wrote: ↑May 13th, 2020, 12:20 am
After posting, I figured this was not what you wanted...
Sorry, but I am not going anywhere near this skin package, as it is not at all interesting for me
Perhaps Mithyr Sar or Yingonito can post an animation...
No problems - was curious - but also not intrigued enough to take a look for myself...
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.
