I'm trying to make my own skin and i have a problem with IfCondition.
Basically, i want skin constantly set specific volume, depending on current volume.
In example below, the first condition works fine, every time i make volume 0, skin toggle mute, but the others don't work at all, when volume equal 10 or 30, nothing happens.
JamHadar wrote: ↑August 24th, 2021, 10:25 am
I'm trying to make my own skin and i have a problem with IfCondition.
Basically, i want skin constantly set specific volume, depending on current volume.
In example below, the first condition works fine, every time i make volume 0, skin toggle mute, but the others don't work at all, when volume equal 10 or 30, nothing happens.
I'm on mobile now so can't test, but just from the top of my head, there isn't such a thing like IfCondition1. The numbering starts at 2, so you'd have IfCondition, IfCondition2, IfCondition3, and so on.
JamHadar wrote: ↑August 24th, 2021, 10:25 am
I'm trying to make my own skin and i have a problem with IfCondition.
Basically, i want skin constantly set specific volume, depending on current volume.
In example below, the first condition works fine, every time i make volume 0, skin toggle mute, but the others don't work at all, when volume equal 10 or 30, nothing happens.
Yincognito wrote: ↑August 24th, 2021, 10:42 am
I'm on mobile now so can't test, but just from the top of my head, there isn't such a thing like IfCondition1. The numbering starts at 2, so you'd have IfCondition, IfCondition2, IfCondition3, and so on.
Oh my god, this is kinda unintuitive to me. Yeah that helped, Thanks.
JamHadar wrote: ↑August 24th, 2021, 11:08 am
Oh my god, this is kinda unintuitive to me. Yeah that helped, Thanks.
Well, it depends on how you look at it. In a way, IfConditionIS what you'd call the 1st IfCondition, aka IfCondition1. For the cases where the option is the sole IfCondition in the measure, it makes little sense to name it IfCondition1 though, especially since it's kinda confusing to have numbered options everywhere, even if numbering would not be needed.
Yincognito wrote: ↑August 24th, 2021, 11:20 am
Well, it depends on how you look at it. In a way, IfConditionIS what you'd call the 1st IfCondition, aka IfCondition1. For the cases where the option is the sole IfCondition in the measure, it makes little sense to name it IfCondition1 though, especially since it's kinda confusing to have numbered options everywhere, even if numbering would not be needed.
Nah, for me, it's 0, 1, 2, 3...n. So, IfCondition is equivalent of IfCondition0 and logical continuation for me is IfCondition1.
JamHadar wrote: ↑August 24th, 2021, 11:29 am
Nah, for me, it's 0, 1, 2, 3...n. So, IfCondition is equivalent of IfCondition0 and logical continuation for me is IfCondition1.
If we had it to do over again, that thinking might have been good. However, due to backwards compatibility, it sorta is what it is...
JamHadar wrote: ↑August 24th, 2021, 11:29 am
Nah, for me, it's 0, 1, 2, 3...n. So, IfCondition is equivalent of IfCondition0 and logical continuation for me is IfCondition1.
Ah, I see. The eternal problem of where to start indexing from: 0 or 1. That depends from implementation to implementation, as already noted...