balala wrote: ↑March 30th, 2019, 9:48 pm
But there is a such side effect: if the leading zeros are not enabled (Show leading zeros unchecked on Settings tool, which means the LeadingZeros variable is 0 in Settings.inc) and the hour has one single digit (before 10 o'clock), when the skin is refreshed, the first zero is hidden which is ok. But if now you click to hide the digits on balls and show the time on the skin, then click again, to put back the digits on balls, the first zero, which should have not to be shown, appears.
Well, as you know, in our area the clock was after 10 o'clock at the time of posting, so I couldn't notice the side effect, since I didn't change the hour. However, since you replied, I did, and while I modified the
IfCondition to the (at least, IMHO) obvious:
Code: Select all
IfCondition=(((#UseBalls#=0)&&([#CURRENTSECTION#]=0)&&(#LeadingZeros#=0))||(#UseBalls#>=1)||(#TimeOnBalls#=0)||((#TimeOnBalls#=1)&&(#LeadingZeros#=0)))
it didn't cancel the side effect (as it logically should have), despite the variables appearing in the log to have the values required to trigger hiding
[MeterLeftTimeDigit]. This is because on clicking to move the digits on the balls,
[MeasureTimeOnBalls] is
directly showing the whole meter group, bypassing the conditions set in
[MeasureTime1Digit] (or any
[MeasureTimeNDigit], for that matter).
I guess my intervention in this wasn't that appropriate, since you obviously know all the little details and dependencies in your skin better than everybody else...