Jsmorley is right - it can't be done to be fully automatic, but it can be achieved through a semi-automatic process - you just have to figure out a way to know the width and the height of the skin to make it work. I did it roughly the way jsmorley explained in my skins, but set the width and the height of the skin as a function of those (initially invisible, in my case) meter widths and heights right from the start, and then used the skin's W/H as parameters in the shape definition.
Maybe you can, if you do something like using Max(Max([WidestMeter:X]+[WidestMeter:W],[AnotherMeter:X]+[AnotherMeter:W]),[LastMeter:X]+[LastMeter:W]) (or something like it) in a Calc formula. I'm just speculating here, but wouldn't this be possible?
EDIT: If the order of evaluation/execution in Rainmeter (aka measures before meters) doesn't get in the way of it, that is (although using dynamic variables might solve it, I'm not sure if on the same skin update or the next)...
Don't be afraid of containers. It's a relatively new option, but easy to work with - you just have to experiment with it.sl23 wrote: ↑October 27th, 2019, 10:02 pmPerhaps this is more related to the new Container function?
It's just that I quite like the whole shape meter as a background. Rounded corners and show Stroke on hover stuff. Useful and subtle which I prefer. Can that be done with Containers? I'm a bit wary of Containers as it looks a bit too much for me!