UnpauseMeasure and DisableMeasure a counter

[AlC]

Hey guys,

I noticed a behaviour with counters and I don't know if it's a bug or normal.

Szenario 1:
Counter (mCalc+1) counts, and when I then disable the calc, the value gets 0. -> Normal

Szenario 2:
Counter (mCalc+1) counts, and when I then pause it, the value stay. -> Normal

Szenario 3:
Counter (mCalc+1) counts, and when I then pause it, then disable it, the value stay. -> Normal or bug? When I disable the measure normally the value should be 0, isn't it?

Szenario 4:
Counter (mCalc+1) counts, and when I then pause it, then disable it, the value stay. And if I then unpause it (the calc is disabled!) the value gets 0. -> strange.

So is this a bug or a normal behaviour?
Hope you understand it

[Brian]

This is all perfectly normal behavior. This is how I designed it anyway. I remember running into the exact same issues when testing, however, the team decided to have behave this way.

When a measure is updated, it first checks if the measure is paused. If it is paused, it returns the current number value (whatever it may be). If it is not paused, it then checks to see if it is disabled. If it is disabled, it returns 0. Else it will return whatever it is measuring.

So although it seems off, you are seeing the correct, designed, behavior. I don't think it would be good skin design to disable a paused measure - or pause a disabled measure.

-Brian

[AlC]

1. Thank you very much for the explanation!
2. Sorry for the late reply, I have to thought about this :)

So although it seems off, you are seeing the correct, designed, behavior. I don't think it would be good skin design to disable a paused measure - or pause a disabled measure.

Sometimes you have to ;)

When a measure is updated, it first checks if the measure is paused. If it is paused, it returns the current number value (whatever it may be). If it is not paused, it then checks to see if it is disabled. If it is disabled, it returns 0. Else it will return whatever it is measuring.

I'm at the beginning of a skin with a lot of calcs and meters, so I look after my CPU. So my question, is then a paused calc "CPU-friendlier" than a disabled calc?

[Brian]

Sometimes you have to

I am not so sure, since the only difference between the two are whether the number value of the measure gets set to 0 or not.

I'm at the beginning of a skin with a lot of calcs and meters, so I look after my CPU. So my question, is then a paused calc "CPU-friendlier" than a disabled calc?

Technically speaking, a paused measure will be faster because it doesn't set any value - it just immediately returns during the update cycle. Whereas a disabled goes the trouble of setting the number value of the measure to 0.

But I highly doubt you would notice any difference between the two as far as CPU usage.

-Brian

[AlC]

I am not so sure, since the only difference between the two are whether the number value of the measure gets set to 0 or not.

It's hard to explain it with my poor english skills, but I save a lot of code if I pause the counters and then (when all counters are paused) unpause and disable them all with one action. Maybe I finish the skin in some days, weeks..

Technically speaking, a paused measure will be faster because it doesn't set any value - it just immediately returns during the update cycle. Whereas a disabled goes the trouble of setting the number value of the measure to 0.

But I highly doubt you would notice any difference between the two as far as CPU usage.

-Brian

Ok, thank you very much again Brian.