KDirWatch emitting dirty signal many times for one change

[Matthias Kretz]

On Wednesday 24 March 2004 18:20, Josef Weidendorfer wrote:
> That doesn't fix the problem with change events occuring when you have
> added a file watch again after saving the file: The latency of the event
> could be quite long. The best is to start a rescan timer on FAM events
> similar to DNOTIFY events.
> Can you check out the attached patch?

If I remove the file before saving I don't get any notifications anymore. Very 
good.
But if I don't remove the file from the watcher I get 312 notifications.

To make it compile I needed to add a definition for slotActivated if 
HAVE_DNOTIFY is undefined.

-- 
C'ya
        Matthias
________________________________________________________
Matthias Kretz (Germany)                          <><
http://Vir.homeip.net/
MatthiasKretz at gmx.net, kretz at kde.org,
Matthias.Kretz at urz.uni-heidelberg.de