KDirWatch emitting dirty signal many times for one change

[Sébastien Laoût]

Hello,

I would want to use KDirWatch in my application.
I use those standards :

I receive all created / modified / deleted signals.
And I store them in a QStringList.
To process them 200 ms later.
The process will do :

For a new file :
	created  received
	modified received
    => I care only the created signal.

For a Save/Change on a file :
	modified received Several times
    => I care only one signal.

For a file deletion :
	deleted received
	deleted received
    => I care only one signal.

For a rename by "mv foo bar" (idem under Konquy) :
	deleted foo received
	created bar received
	deleted foo received
    => I considere this special configuration as a rename
    => Because it's the only one that reflete a rename / move.

My questions :

- Are you about to process the 200 ms by KDE libs and do not send
[deleted, created, deleted] suite ? So I could to not be able to detect
renamings in the future ?
- Is this schemas of renaming detection valable for all computers ? I've
readed about FAM, DNOTIFY, FAM/DNOTIFY but don't know very well all that
is...
- Is their another way to detect renaming ?

Because detect the renamings is fundamental for my app...
So I need it.

Thank you to clarify my mind...