DirectoryWatcher - bug & doc error

Question

I've set up a DirectoryWatcher event to monitor a shared
directory on a network (CF7.01 Ent on Win2003 has full R/W/D
permissions). I've noticed two quirks, possibly bugs or
undocumented "features".
1) The interval setting in the config file is ignored and the
event is triggered the moment a new file is added. The
documentation says the directory is only checked at the interval
specified in the config file which defaults to 60000ms (60sec). I
suspect this setting is for Unix flavours of CF only but can't find
documentation to suggest that CF on Windows will ignore the
interval setting.
2) I'm only using the addFunction=onAdd event but this is
called twice whenever a file is added. If 1 file is added it gets
run twice, if 3 files are added it runs 6 times. I added some code
within the onAdd function to log whenever it's executed and this
confirms it's run twice when a new file is added. (New files are
created by a different CF server on the network.)
The documentation says to set the changeFunction and
deleteFunction "to nothing" if you don't want them monitored, so I
did. However, I have reason to believe the changeFunction is still
executed despited the line "changeFunction=" without any value.
I tried a test and disregarded the documentation and
commented out the changeFunction and deleteFunction lines in the
config file and hey presto, the "addFunction=onAdd" function is now
executing just once per file!
This suggests there is 1 bug and 1 documentation error. The
bug is something like "changeFunction=" will actually execute the
onAdd event (CF's wiring must be mixed up), hence a new file will
execute onAdd twice. The documentation error is that "set to
nothing if you don't want to see these events" should actually say
"remove or comment out these lines if you don't want these events
to be triggered".
Gary.

Answer 1

Hi Russ,
same issue here (FM 11, Win7). I'm not sure, but in my opinion it's an error in the documentation. The values for ComponentType should be:
Constants.FV_BK_FOLDER (0x2): Folder
Constants.FV_BK_GROUP (0x40): Group
Constants.FV_BK_FILE (0x200): File
Additionally you could check the sort of file type via BookComponentFileType (FM, MIF, XML, Ditamap).
In a short test script for traversing a hierarchical book the BookComponentFileType has some more values:
Constants.FV_BK_FOLDER (0x2): Folder
Constants.FV_BK_BOOK (0x4): Book (inside another book)
Constants.FV_BK_FM (0x8): FrameMaker document
Constants.FV_BK_MIF (0x10): MIF document
Constants.FV_BK_XML (0x20): XML document (also Ditamap and Bookmap)
Constants.FV_BK_GROUP (0x40): Group
The main difference between ComponentType and BookComponentFileType seems to be the more detailed information about the file type.
Best Regards, Andreas
Message was edited by: justBE