I Give Up - Why is the Timer in Tile #2's Footer?

[michicago]

1) Give a description of the problem
The timer value shows up in tile 2… it actively counts down, and even changes to “pending” during piston execution. I haven’t set it to be there… I have tried clearing the piston tile to see if some lingering value stuck it there… so far it has proven stealthy and invincible.

This hasn’t stopped the piston from doing what I want it to - this is more of a curious, let’s see if we can figure out what’s going on ‘problem’.

2) What is the expected behavior?
Tile 2 footer should be empty

3) What is happening/not happening?
(PUT YOUR INFO HERE)

4) Post a Green Snapshot of the piston

5) Attach any logs (From ST IDE and by turning logging level to Full)
The log below includes the clearing of tiles and the setting of Tiles 1, 2, and 3. I see no reference to the timer value in the piston, but it’s staring right at me in Tile 2’s footer.
`(1/16/2018, 9:59:59 AM +147ms

+1ms ╔Received event [Home].time = 1516114800000 with a delay of -853ms
+269ms ║RunTime Analysis CS > 19ms > PS > 54ms > PE > 196ms > CE
+273ms ║Runtime (55945 bytes) successfully initialized in 54ms (v0.2.101.20171227) (270ms)
+274ms ║╔Execution stage started
+290ms ║║Cancelling statement #104’s schedules…
+294ms ║║Executed virtual command clearTile (0ms)
+300ms ║║Cancelling statement #104’s schedules…
+303ms ║║Executed virtual command clearTile (0ms)
+310ms ║║Cancelling statement #104’s schedules…
+313ms ║║Executed virtual command clearTile (1ms)
+319ms ║║Cancelling statement #104’s schedules…
+323ms ║║Executed virtual command clearTile (0ms)
+329ms ║║Cancelling statement #104’s schedules…
+332ms ║║Executed virtual command clearTile (0ms)
+339ms ║║Cancelling statement #104’s schedules…
+342ms ║║Executed virtual command clearTile (1ms)
+348ms ║║Cancelling statement #104’s schedules…
+351ms ║║Executed virtual command clearTile (0ms)
+358ms ║║Cancelling statement #104’s schedules…
+361ms ║║Executed virtual command clearTile (1ms)
+367ms ║║Cancelling statement #104’s schedules…
+371ms ║║Executed virtual command clearTile (0ms)
+377ms ║║Cancelling statement #104’s schedules…
+381ms ║║Executed virtual command clearTile (1ms)
+387ms ║║Cancelling statement #104’s schedules…
+391ms ║║Executed virtual command clearTile (0ms)
+398ms ║║Cancelling statement #104’s schedules…
+401ms ║║Executed virtual command clearTile (1ms)
+407ms ║║Cancelling statement #104’s schedules…
+411ms ║║Executed virtual command clearTile (0ms)
+419ms ║║Cancelling statement #104’s schedules…
+423ms ║║Executed virtual command clearTile (0ms)
+429ms ║║Cancelling statement #104’s schedules…
+432ms ║║Executed virtual command clearTile (0ms)
+438ms ║║Cancelling statement #104’s schedules…
+442ms ║║Executed virtual command clearTile (0ms)
+445ms ║║Cancelling statement #73’s schedules…
+875ms ║║Calculating (string) 31 + (string) ° / >> (string) 31° /
+879ms ║║Calculating (string) 31° / + (string) 31 >> (string) 31° / 31
+883ms ║║Calculating (string) 31° / 31 + (string) ° >> (string) 31° / 31°
+886ms ║║Calculating (string) 31° / 31° + (string) 75% >> (string) 31° / 31° 75%
+889ms ║║Calculating (string) 31° / 31° 75% + (string) >> (string) 31° / 31° 75%
+957ms ║║Calculating (string) :wu-v3- + (string) partlycloudy >> (string) :wu-v3-partlycloudy
+961ms ║║Calculating (string) :wu-v3-partlycloudy + (string) : >> (string)
+964ms ║║Calculating (string) :wu-v3-nt_ + (string) partlycloudy >> (string) :wu-v3-nt_partlycloudy
+967ms ║║Calculating (string) :wu-v3-nt_partlycloudy + (string) : >> (string)
+980ms ║║Calculating (string) Wind: + (string) 0.0 >> (string) Wind: 0.0
+983ms ║║Calculating (string) Wind: 0.0 + (string) >> (string) Wind: 0.0
+987ms ║║Calculating (string) Wind: 0.0 + (string) NNW >> (string) Wind: 0.0 NNW
+990ms ║║Calculating (string) Wind: 0.0 NNW + (string) Gusts: >> (string) Wind: 0.0 NNW Gusts:
+993ms ║║Calculating (string) Wind: 0.0 NNW Gusts: + (string) 0 >> (string) Wind: 0.0 NNW Gusts: 0
+1009ms ║║Executed virtual command setTile (2ms)
+1029ms ║║Calculating (string) 7:24AM + (string) / >> (string) 7:24AM /
+1033ms ║║Calculating (string) 7:24AM / + (string) 5:25PM >> (string) 7:24AM / 5:25PM
+1042ms ║║Calculating (string) Rise + (string) >> (string) Rise
+1046ms ║║Calculating (string) Rise + (string) Set >> (string) Rise Set
+1054ms ║║Executed virtual command setTile (2ms)
+1064ms ║║Cancelling statement #84’s schedules…
+1482ms ║║Executed virtual command setVariable (5ms)
+1516ms ║║Executed virtual command setVariable (4ms)
+1556ms ║║Executed virtual command setVariable (4ms)
+1596ms ║║Executed virtual command setVariable (19ms)
+1603ms ║║Calculating (decimal) 0.0 + (decimal) 3.0 >> (decimal) 3.0
+1634ms ║║Calculating (string) + (string) 3 >> (string) 3
+1643ms ║║Calculating (integer) 3 > (integer) 0 >> (boolean) true
+1663ms ║║Calculating (string) / + (string) 5 >> (string) /5
+1672ms ║║Calculating (integer) 5 > (integer) 3 >> (boolean) true
+1683ms ║║Calculating (string) :wu-v3- + (string) clear >> (string) :wu-v3-clear
+1690ms ║║Calculating (string) :wu-v3-clear + (string) : >> (string)
+1695ms ║║Calculating (string) + (string) 3 >> (string) 3
+1701ms ║║Calculating (string) 3 + (string) /5 >> (string) 3/5
+1743ms ║║Calculating (string) + (string) 0 >> (string) 0
+1749ms ║║Calculating (string) 0 + (string) " >> (string) 0"
+1758ms ║║Calculating (decimal) 0.0 > (decimal) 0.0 >> (boolean) false
+1789ms ║║Calculating (string) + (string) 0 >> (string) 0
+1794ms ║║Calculating (string) 0 + (string) " >> (string) 0"
+1799ms ║║Calculating (decimal) 0.0 > (decimal) 0.0 >> (boolean) false
+1809ms ║║Calculating (string) 29 + (string) ° >> (string) 29°
+1817ms ║║Calculating (string) 29° + (string) >> (string) 29°
+1823ms ║║Calculating (string) 47 + (string) ° >> (string) 47°
+1831ms ║║Calculating (string) 47° + (string) >> (string) 47°
+1843ms ║║Executed virtual command setTile (2ms))`

[Mike1616]

I’ve absolutely seen that in my own pistons as well. Purposely putting in a blank value for the footer causes it to display the piston timer down there. I’ve largely ignored it, so perhaps this is a good thing to track down the root cause of this behavior.

What I did to no longer see the thing though was to just display any text down there and set it to be the same color as the background.

Clearly that’s just hiding the behavior though…not figuring out why it happens that way.

[michicago]

Maybe @c1arkbar knows?

I’m stumped on this one… if it’s just a known “defect” I can live with that. But not being able to figure out why it’s there is driving me crazy.

[c1arkbar]

Probably a bug somewhere. I’ve moved this to the bug reporting category

@ipaterson

[ipaterson]

Well, it’s explicitly added in there. I would say it probably shouldn’t be but perhaps people require that. Here is the value of the tile footer text broken down into a few lines with comments that might explain what’s going on:

// If there is any footer text
piston.meta.s['o' + ($index + 1)]
// Then show it
? renderString(piston.meta.s['o' + ($index + 1)])
// Otherwise
: (
    // If there is a timer
    piston.meta.n
    // Then show it
    ? timeCounter(piston.meta.n)
    // Otherwise leave the footer blank
    : ' '
)

[eibyer]

Hmm, I believe someone asked for it a looooong time ago when tiles was in its early stages. Will have to check the old ST threads later.

[c1arkbar]

Thanks for the info @ipaterson

So if you want to get rid of the timer then just set the footer text to a space or some text that has the same fore- and background colors.

[eibyer]

Found it… (sorry, just got back home )

[michicago]

That post was in no danger of being found by me! lol… I was just trying to figure out what in my piston was doing it. Interesting ‘feature’… not sure I understand what it’s overcoming, but now I know how to work around it.

Thanks!