Zugg Software :: View topic

Beginner Joined: 12 May 2003 Posts: 24

I have the gauges button set up correctly as far as I can tell. And the variables are all set. As are my triggers. Here is my example.

search
You search around, blah blah.
Roundtime 10 sec.

I have the following triggers.

#TRIGGER {^roundtime (%n)} {#if (@rtmax>0) {
#var rtmax @rtcurrent
#add rtmax %1
#add rtcurrent %1
} {
#var rtmax %1
#var rtcurrent %1
}}

#TRIGGER ((@rtcurrent>0)) {
#wait 1000
#add rtcurrent -1
#GAUGE RT "" @rtcurrent @rtmax
}

#BUTTON 1 {} {} {} {} {@rtcurrent} {} {} {} {} {} {} {} {} {32842} {} {Gauge||12|@rtmax||0} {} "" {Explore|Inset} {} {RT}

Now then, with all that said. I can do a #show @rtcurrent and see the value counting down. If I right click on the gauge and hit refresh on the settings screen, and then click back on the main window with the guage, it updates, but I cannot get it to update on it's own. Any ideas on what I can check out?

Beginner Joined: 12 May 2003 Posts: 24

Oh, and on a side note, it seems the triggers I use to send other "patterns" to other windows don't function during this time either. Maybe something is stopping the triggers from working correctly?

GURU Joined: 10 Oct 2000 Posts: 4379 Location: USA

It's the #WAIT command. You should avoid using this command and replacing it instead with #ALARM's. Here are two examples:
#TRIGGER {some pattern} {#WAIT 1000;other commands}

transforms to:
#TRIGGER {some pattern} {#ALARM {+1} {other commands}}

#TRIGGER {some pattern} {#WAIT 2000;some commands;#WAIT 1000;other commands}

transforms to:
#TRIGGER {some pattern} {#ALARM {+2} {some commands;#ALARM {+1} {other commands}}}

Kjata

Beginner Joined: 12 May 2003 Posts: 24

When I use #alarm, it counts down very strangely. Almost like 2 "seconds" off the counter every second.

#TRIGGER ((@rtcurrent>0)) {#alarm {+1} {#add rtcurrent -1}}