clk() and tickClk() in the same Expression2

[shadowscion]

Individually, they both seem to work fine, but when you use them in the same chip, the clk block will not execute. Ex. code:

if (first()) {
runOnTick(1)
SPAM = "spammyspam"
} elseif (tickClk()) {

} elseif (clk()) {
print(SPAM)
}
interval(500)

Yes the runOnTick is completely useless for this code, but its just an example of how to reproduce the bug. Using both of these in the same chip is essential for optimization in a lot of projects. BTW, are there code tags for these comments?

[TomyLobo]

4 backticks initiate and terminate a code block

Can you test this piece of code and report back what it results in?

interval(500)
runOnTick(1)
if (clk()) {
print("clk")
}
if (tickClk()) {
print("tickClk")
}

[shadowscion]

Ah.

With that code, like the one I posted, the clk() portion gets ignored.

[Nebual]

interval(500) is identical to timer("interval", 500). What is occuring in both test codes, is that every tick you're resetting the "interval" timer to trigger in 0.5 seconds, which never lets it get below 0.47 before being reset again. I wouldn't call this a bug so much as an oddity, as it can be useful to disable/change/reset the interval timer after it has been set, though I certainly have been confounded by this myself in the past.

if(first()) {
    runOnTick(1)
    interval(100)
    timer("10s", 10000)
} elseif(tickClk()) {
    #Physics
} elseif(clk()) {
    interval(500) #Trigger this every 0.5 seconds
    #Calibration
} elseif(clk("10s")) {
    timer("10s",10000) #Trigger this every 10 seconds
    print("All is still well!")
}

Perhaps theres a wiki page that could be made more clear...

[shadowscion]

I wasn't aware interval could be set within first()