Volume Change and ToggleMute Substitute="-1":"0"

[balala]

Here is the skin group rmskin for reference:
Music Controls_1.3.xx.rmskin

This package has five .ini skin files. Which one have we to work with?

[balala]

These are my Measure and Meter.

Instead of making a substitution on the [Percent] measure, I'd use a Clamp function to limit the returned value:

Code: Select all

[Percent]
Measure=Calc
Formula=( Clamp ( MeasureVolume, 0, 100 ))

[Yincognito]

Thanks Yincognito
I tried your suggestion but no success.
These are my Measure and Meter.

Yeah, it looks like I have to check your skins, after all, because my posted example works 100% so it must be something in your skins that's preventing the expected result... Will take a look at them in a moment.

[Yincognito]

This package has five .ini skin files. Which one have we to work with?

His first posted code is from Round iTunes, the subsequent code is from Small Vol, and here lies the problem, see my following reply.

[Yincognito]

Thanks Yincognito
I tried your suggestion but no success.

Yeah, figured out what the problem is. You need to set Text=[Percent]% in your [PercentString] meter from the Round iTunes\music_big.ini skin and the 0 will appear. The reasson is simple: when you set it to Text=[Percent:0]%, the meter displays the number value of that measure, which I already told you it can't be directly modified; on the other hand, when set to Text=[Percent]%, the meter displays the string value of that measure, which is properly substituted with "0".

[Mor3bane]

Yeah, figured out what the problem is. You need to set Text=[Percent]% in your [PercentString] meter from the Round iTunes\music_big.ini skin and the 0 will appear. The reasson is simple: when you set it to Text=[Percent:0]%, the meter displays the number value of that measure, which I already told you it can't be directly modified; on the other hand, when set to Text=[Percent]%, the meter displays the string value of that measure, which is properly substituted with "0".

Such a simple solution!
I've been trying to break the skin to identify any error in code flow. But this was unexpected. I looked at it and looked at it but the zero seemed so 'necessary'. I now know that was not the case.

It is almost release time for version 2 of this mini suite.

Thanks Yincognito (once again).

[Yincognito]

Such a simple solution!
I've been trying to break the skin to identify any error in code flow. But this was unexpected. I looked at it and looked at it but the zero seemed so 'necessary'. I now know that was not the case.

It is almost release time for version 2 of this mini suite.

Thanks Yincognito (once again).

No worries - glad to help. As you can see, it sometimes pays off to be aware of the little details in the manual...

[balala]

You need to set Text=[Percent]% in your [PercentString] meter from the Round iTunes\music_big.ini skin and the 0 will appear.

The disadvantage of this approach is that it requires to set the dynamic variables. If you put a MeasureName=Percent and you use a simple Text=%1% option on the same string meter, you can avoid setting the dynamic variables.

[Yincognito]

The disadvantage of this approach is that it requires to set the dynamic variables. If you put a MeasureName=Percent and you use a simple Text=%1% option on the same string meter, you can avoid setting the dynamic variables.

Well, I only corrected the existing code to solve the issue that was referenced to. As for the rest, you're right of course, there's no need to have section variables there in theory, but then, I have no idea what other reasons are there to justify its presence...

[Mor3bane]

The disadvantage of this approach is that it requires to set the dynamic variables. If you put a MeasureName=Percent and you use a simple Text=%1% option on the same string meter, you can avoid setting the dynamic variables.

Thanks, I changed to your recommedation.

Well, I only corrected the existing code to solve the issue that was referenced to. As for the rest, you're right of course, there's no need to have section variables there in theory, but then, I have no idea what other reasons are there to justify its presence...

No apparent issues, so all is good afaik.