Zugg Software :: View topic

Wanderer Joined: 07 Oct 2001 Posts: 71

For one of my delay aliases I have it create a standar + alarm trigger
followed with a command line to reduce the time by .4 seconds that looks like...

#NOOP %alarm( Delay, <%eval( %eval( @delay*1000)-400)>)

It works how it should, reducing the time by 400 milliseconds. However, the < > are giving a syntax error in the editor window.

Without the < > the #NOOP line fails to work.

Suggestions, comments, questions?

Like I said, it DOES work, just the error bothers me - and with the error it won't auto align everything Very Happy

Wizard Joined: 15 Jan 2002 Posts: 1644 Location: USA

hmmm

try using
{} or () or 's instead of <>

Wanderer Joined: 07 Oct 2001 Posts: 71

No, neither the {} or () worked. They don't force the expansion of the %eval statements like the <> do. Typically the <> do not seem to be needed, becuase usually it expands on its own fine. But used with the %alarm function it won't work without the <> - which gives the syntax error. Sad

Apprentice Joined: 29 Jun 2001 Posts: 198 Location: USA

Have you tried using the double quote " instead of < and >?
Or
#Math NewDelayTime (@delay*1000)-400))
#NOOP %alarm( Delay, @NewDelayTime)

Wanderer Joined: 07 Oct 2001 Posts: 71

quotation marks did not work either. And I tried the style of #NOOP %alarm( Delay, @NewDelayTime) it will only work in the same manner #NOOP %alarm( Delay, <@NewDelayTime>)

Wanderer Joined: 17 Aug 2004 Posts: 98 Location: OK, USA

Did you try #CALL instead of #NOOP?

Wizard Joined: 14 Oct 2000 Posts: 1368

I think this is a bug and it shows a possible design issue in zMUD. Zugg probably has to add handling for arguments separately each time he defines a new function so it isn't odd these things occur.

Workaround:
#exec {~#noop ~%alarm( Delay, %eval( @delay*1000-400))}

Apprentice Joined: 29 Jun 2001 Posts: 198 Location: USA

I'm not sure you actualy need the %eval, assuming @delay has an integer value stored in it.
#NOOP %alarm(Delay, ((@delay*1000)-400))

Wizard Joined: 14 Oct 2000 Posts: 1368

Wanderer Joined: 07 Oct 2001 Posts: 71

#exec {~#noop ~%alarm( Delay, %eval( @delay*1000-400))}

and

#CALL %alarm( Delay, %eval( %eval( @delay*1000)-400))

did not work.

#CALL %alarm( Delay, <%eval( %eval( @delay*1000)-400)>)

still gave the syntax error

Oh well, I guess it is a little flaw, and I'll just keep working with the <> and the syntax error

Apprentice Joined: 29 Jun 2001 Posts: 198 Location: USA

Wanderer Joined: 07 Oct 2001 Posts: 71

mmm, nope just threw that into my settings and

#NOOP %alarm(Delay, ((%int(@delay)*1000)-400))

did not cut it either. Sad

Apprentice Joined: 29 Jun 2001 Posts: 198 Location: USA

Is there a possibility that you've changed some of the default settings that would affect any of these suggestions?
Or is there something else in your script that would affect it?

Apprentice Joined: 29 Jun 2001 Posts: 198 Location: USA

I decided to test these things out.
The #EXEC example above did work for me. The other examples only seemed to reset the alarm to its original time setting, seemingly to set the setTime parameter as its original value.

I set this alarm:

Wanderer Joined: 07 Oct 2001 Posts: 71

Yes, I do have to apologize, I put in the code once again and you're correct in that the #EXEC method does work. I must've mistyped something when I tried it previously. Great work Very Happy