Directory compare notification not considering filtered file

General questions about using ExamDiff Pro, ideas for new features, bug reports, and usage tips.
Post Reply
lpaparel
New Member
Posts: 5
Joined: Wed Feb 18, 2009 9:22 am

Directory compare notification not considering filtered file

Post by lpaparel »

Issue when comparing directories and a file within the directory has been modified that i filtered. The following message is displayed "The first directory of one of its sub-directories has been modified outside of Examdiff Pro. Do you want to recompare the directories".

I want to keep this message for all files (that I don't have filtered), however e.g. *.log, or *.tmp files that are changed should not be considered for this notification.

Another scenario is that the actual datestamp of the directory has changed (when the file within in changed), and this is what triggered the change notification.

I cannot find any options to ignore directory timestamps during directory compares.
User avatar
psguru
Site Admin
Posts: 2396
Joined: Sat May 15, 2004 4:23 pm
Location: California
Contact:

Re: Directory compare notification not considering filtered file

Post by psguru »

I want to keep this message for all files (that I don't have filtered), however e.g. *.log, or *.tmp files that are changed should not be considered for this notification.
Correct, currently even filtered out files/directories cause change notifications. We'll try and fix this in 4.5 (now in Beta).
Another scenario is that the actual datestamp of the directory has changed (when the file within in changed), and this is what triggered the change notification.
I cannot find any options to ignore directory timestamps during directory compares.
There's no such option. But how common is this scenario?
psguru
PrestoSoft
lpaparel
New Member
Posts: 5
Joined: Wed Feb 18, 2009 9:22 am

Re: Directory compare notification not considering filtered file

Post by lpaparel »

The scenario that the directory timestamp is changed happens whenever a file within that directory changes. This is our case. I am only assuming that the notification picks this up. If the notification only looks at the actual file changes within directory, then this is not an issue. However if it does look at the actual folder timestamp... then this will be an issue since it happens very often as files are changing on a regular basis within that directory.
User avatar
psguru
Site Admin
Posts: 2396
Joined: Sat May 15, 2004 4:23 pm
Location: California
Contact:

Re: Directory compare notification not considering filtered file

Post by psguru »

I'm not sure that the directory timestamp changes when its file are changed but it's a good point, and if it's the case, filtering out changes may become a problem. We'll investigate this further.
psguru
PrestoSoft
Post Reply