forum.vdsworld.com

Serge · Posted: Tue Mar 18, 2003 2:55 am Post subject: @timer(1,v)

hi all,

i wrote a program that uses timers and that makes use of @timer(1,v)

a user has reported a problem with the code that follows on from the return of @timer(1,v) and i was wondering if different o/s report something different when that call is made

i am using win me and my program works fine, he is using w2k and reports a problem

here is the part of the code that causes a problem for him, and it would be the case if @timer(1,v)returns a different string under w2k then it does under win me

SnarlingSheep · Posted: Tue Mar 18, 2003 3:12 am Post subject:

In your code you have:
elsif @equal(@len(%%timer),14)
I think that might gave ya some problems Smile

Serge · Posted: Tue Mar 18, 2003 3:35 am Post subject:

thanks snarling sheep but i find that the output of @timer(1,v) is either 14 or 15 characters long (under me) and i need to deal with both possibilities

Serge

SnarlingSheep · Posted: Tue Mar 18, 2003 3:38 am Post subject:

I understood that part, but as far as I know "elsif" is not a part of VDS Smile

ShinobiSoft · Posted: Tue Mar 18, 2003 3:44 am Post subject:

Hey Sheep,

Actually "elsif" is a new command introduced in VDS 4. Or at least VDS 4.5
because it's in my documentation and I also use it. Smile

ShinobiSoft · Posted: Tue Mar 18, 2003 3:49 am Post subject:

Hi Serge,

How are you setting the initial value of the timer? I mean what time format
are you using?

SnarlingSheep · Posted: Tue Mar 18, 2003 3:50 am Post subject:

Doh, I never noticed it. I even tried it to make sure, it didn't turn bold in the IDE so I figured it didn't exist.
Turns bold now though and works.
So, don't mind me..the length is either 14 or 15 for me on XP Pro here.
Any way to find out what the length actually was on the users system?
Only thing I can think of(now that I've been proven stupid..that was hard huh?) is it could possibly have something to do with regional settings.

ShinobiSoft · Posted: Tue Mar 18, 2003 3:57 am Post subject:

lol, I wasn't trying to make ya feel stupid Sheep. Shocked

Sorry

SnarlingSheep · Posted: Tue Mar 18, 2003 3:58 am Post subject:

LoL, I do a good enough job on my own, trust me Wink

ShinobiSoft · Posted: Tue Mar 18, 2003 4:00 am Post subject:

Sheep, I think you might be onto something with the Regional settings
suggestion.

Serge · Posted: Tue Mar 18, 2003 9:51 am Post subject:

thanks for your help guys Smile

i will write a small program that will put into a text file what my user gets when vds runs @timer(1,v)...it'll be interesting to see what the problem might be

as for the regional setting, i would be surprised by that because the user is in australia same as me

would it be possible for me to see what various o/s return when vds issues a @timer(1,v) command, perhaps the structure is different even though the length is the same

could i have, pretty please, the return string of @timer(1,v) for nt, xp, xp pro and w2k...just in case there's something i'm missing

thanks in anticipation

Serge
ps my user ran the program on win95 and has no problems, but he can't run under w2k

SnarlingSheep · Posted: Tue Mar 18, 2003 5:21 pm Post subject:

Give us an example of the timer you are using in your program Serge so we can make sure we test it right. Smile

Serge · Posted: Wed Mar 19, 2003 7:29 am Post subject:

now i am really puzzled

i wrote a test program that records what @timer(1,v) returns and this is what my user obtained

ShinobiSoft · Posted: Wed Mar 19, 2003 8:01 am Post subject:

I have one question for ya Serge. The following code:

ShinobiSoft · Posted: Wed Mar 19, 2003 8:35 am Post subject:

Please disregard my previous post. I'm running Windows 98SE and I can't
duplicate the problem on my machine.

I do, however, have a couple of suggestions:
1) the %%time_separator_1 and %%time_separator_2 variables are not
necessary. Mainly because they make the code hard to read and they
don't serve any real purpose.

2) You can just as easily set the timer like this: