Hello.
I want to use a method of reverse relative position.
I have an image meter which serves as a base object for other meters like String meters. Because I have many such base objects which have many string meters it is quite repetitious and I don't want to use every time same formulas with a small change for all the string meters. Let's take a look at my example (I can change in any way you recommend saving the concept).
I want to use same MeterStyle for all string meters in a way that they all take Y of MeterN. In other words I want [MeterNText1:Y] to be placed relatively to corresponding Y of [MeterN] of the same N. How to approach this?
P.s. I am not quite sure if it is called reverse relative position but it looks like that for me.
fonpaolo wrote:...while, in a similar situation, I always copy and paste one section to the next, modifying only something here and there*.
...call me crazy.
*I did it 120 times in one skin...
Exactly why I want to achieve this with just one MeterStyle so I don't change it here and there. Just to have one single place to do such a simple task.
Active Colors wrote:Exactly why I want to achieve this with just one MeterStyle so I don't change it here and there. Just to have one single place to do such a simple task.
Yes, but take into account that Rainmeter isn't a programming language and you probably won't be able to do something like what you want in Rainmeter. Probably fonpaolo is right and you have to make a few (or much more?) copy, paste and modification operations.
Me at least don't see any way to make what you want through Rainmeter code.
Probably it's what you do, I try to standardize the code using relative positioning of all the meters of the section to the first, then I copy and paste to a new section and I only modify the names of the meters (MeterX_1, 2, A, B and so on)and maybe the group name if/when needed.
I don't think I've reinvented the wheel...
Seems that is the whole purpose - coding repetitive functions in fewer lines of code?
Ya'know... a function creates b functionc = b, b is the new line of code, c becomes a, then a tells b what to be. rinse and repeat in an if then or even a for loop, maybe a do while?
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.