I think I may just be fried with 15 hours of reading, coding and rereading. I know what I need to be working with is counters, but my brain is mush at this point of the night. I need to (based on Measure=Time Format=%S) {{or no Format=%S if I don't need it}} to set 2 different variables for a meter on the next update, then to a different set the next update and then back to the original the next update. Back and forth with each new update. This should be simple but I'm my brain hurts right now.
Here's the ugly code I have. Should explain what I'm trying to do. I know it's wrong, mostly because it doesn't work. heh
I read the manual, forums and look at codes to other skins, and I swear it's like being able to slightly read another language but not being able to write in it.
Im looking to have the skin alter between two .png's every second. The problem I have run into with trying to this with a counter is that I'm going between "on and off" for the most part, or "1 or 2". Because the counter doesn't take effect til the next update, it gets stuck on 1. I don't know. I figure the solution is simple and will be a total facepalm moment when I see it. For now, this code works but is a waste of CPU seeing how there are 60 measures running for this two-step-repeat process.
This is the same problem. I'm trying to see if I can use the animated "bitmap" technique, switching perfectly in time with %S, rather the Rotation. I may try them both once I solve this, and see which works better with the least CPU.
The [MeasureSwitch] measure will alternate between 1 and 2 every Update (which is 1000, or once a second) then the IfActions on the measure will set the ImageName option on the Image meter to the desired .png.
You can use the same counter, changing the !SetOption to set a RotationAngle on a Rotator meter, change the ImageTint on an Image meter. Whatever fits the bill for you. You can have it do more than one thing by putting each action inside "[]" brackets.
You do need to be careful about having it use !SetVariable to set the value of a variable, as you will be one "Update" out of sync, as the change to the variable will happen on update 1 and the "use" of the variable by other meters or measures will happen on the next update, or update 2.
Unfortunately the skin already is running with an Update=100 and am wanting to link the toggle with actual %S rather then attempting to just UpdateDivider=10 because the toggle ends up being off from real time.
I can't tie a [MeasureSwitch] to a [MeasureTime] and then attempt to use a Formula to do "(MeasureSwitch % 2) + 1" because it requires a "Calc" as the "Measure=". example:
That doesn't work, going the long way with 60 measures that (Measure=Time, Format="%S", IfEqualValue=01, IfEqualAction=!) does work with Time on an Update=100 skin.
Would there be a shorter way of doing this in this situation? Yeah the !SetVariables doesn't work because of the Update delay if it was tied to Measure=Time, and would be toggling 10 times if it was tied to the Update=100 which tends to not be synced with Time.
I need a really clear description of the end result you wish to achieve.
GitHub | DeviantArt | Tumblr
This is the song that never ends. It just goes on and on my friends. Some people started singing it not knowing what it was, and they'll continue singing it forever just because . . .
GitHub | DeviantArt | Tumblr
This is the song that never ends. It just goes on and on my friends. Some people started singing it not knowing what it was, and they'll continue singing it forever just because . . .
It's a pendulum for a clock set to Measure=Time. Swing right (1 second) swing left (1 second) and so on. Just tested my Animated Bitmap method and it hiccups. Looks as if I'm left with just making an Animated Bitmap that runs out of sync with the rest of the clock or just abandon it altogether
