David A. Desrosiers wrote:
Oops! Nevermind: I found my bug.
Don't keep us all in suspense... what was it? ;)
I was too quick. I thought I had forgotten to check for the error
return from the vfs db info call, but I hadn't forgotten. So I still
don't have it. Hmm. Here's an idea. I'll se
Oops! Nevermind: I found my bug.
Don't keep us all in suspense... what was it? ;)
d.
___
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
Oops! Nevermind: I found my bug.
Alex
___
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
My suggestion is to check for a .pdb or .prc extension (depending on
what we are searching for) before calling VFSFileDBInfo(). The
other advantage of doing this is that it would speed up the VFS scan
since we wouldn't have to open some of the files.
That would probably miss a lot of Plucker
My ClieSkinner program (see http://www.zlthemes.com/Programs.php) uses
the same method as Plucker to scan for files in VFS, namely iterate over
the directory and call VFSFileDBInfo(). Unfortunately, two users have
reported hangs as a result of using this method. My hypothesis is that
they had