forum.vdsworld.com

ColdWind · Newbie Joined: 18 Apr 2001 Posts: 12 Location: UK

How can i use a list and get a program to automaticly select the next item in a loop until there are no more items...

Garrett · Posted: Sat Dec 29, 2001 10:15 pm Post subject:

Que · Posted: Wed Jan 02, 2002 6:56 pm Post subject: MTZip

FYI - I had some difficulty with the dll files included with the mtzip.dll
The file names did not match up with what the mtzip.dll was looking for.
renaming them did not work. I ended up searching the web and finding
newer versions of the necessary files. This worked, but I had to turn off
mtzip error messages. Also, mtzip.dll requires that the 3 necessary DLL
files reside in the application directory ie. @path(%0)

I'm not sure how far you are with your zip prog, but if you want, I could
send a copy of what I threw together.... simple resizable drag drop
interface. Simply functional.... low on features, but shows the use of the command.

thx.
Que

iMPA · Newbie Joined: 26 May 2001 Posts: 9 Location: Spain

simple, not optimized, dirty and ugly piece of code... nor it works...
extract all files in the zip to the zip directory...

ColdWind · Newbie Joined: 18 Apr 2001 Posts: 12 Location: UK

Mac · Posted: Thu Jan 03, 2002 12:46 am Post subject:

I've had problems with @next() being dependable. I use
a method similiar to iMPA for REPEAT/UNTIL Loops:

Que · Posted: Thu Jan 03, 2002 7:54 pm Post subject: Repeat

I used the following:

REPEAT
mtzip add,buffer,@next(1)
UNTIL @not(@ok())

This doesn't require a separate count variable

Mac · Posted: Fri Jan 04, 2002 10:23 pm Post subject:

That's true, but on my Win95 system @next() does NOT
work correctly all the time (and apparently on others also).
It does work most of the time, and I'd prefer to use it were
it dependable.

A couple of weeks ago I was helping an individual with
a VDS program at a genealogical library, and I sent him
a routine using @next(). It worked perfectly with the
small sample data file he sent, but when he tried the
larger data file, it quit. So I sent the method with the
incrementing variable, and it worked fine.

This wasn't the first time I've had problems with it, but
it's probably the last time I'll try to use it. If you want
a routine to work correctly on all platforms and situations,
I'd go with the incrementing variable and @item().

Cheers, Mac

Tommy · Posted: Fri Jan 04, 2002 11:01 pm Post subject:

Mac,

I don't think @next() is platform dependend. Anyway, you may want to try to combine it with the @index() function. Also sometimes you may have to use list seek to set the index pointer as appropriate. If you utilize it correctly, it won't trouble. Remember that @next(), like @item() returns the current item, and only once it's returned, it increases the index pointer by one. @count() returns one higher number than the numbers returned by @index(), as the indexes start by 0.

Mac · Posted: Fri Jan 04, 2002 11:32 pm Post subject:

I know exactly how @next() works Tommy. I've tried many
times to use it, and it works fine MOST of the time, especially
on smaller programs.

I'm just sharing my experience with it. The platform may not
have anything to do with it, but the more complicated the code,
the less dependable it is (especially in loops).

Like I said, if it was dependable I'd prefer using it.

Cheers, Mac