Hello Allie, Wednesday, August 18, 2004, 21:39 you wrote at mid:[EMAIL PROTECTED]
>> So I think the best solution is, that TheBat! do its action like they >> are listed in NFS: >> <flag message> >> <copy message> >> <park message> >> means, that the copies are flagged, but not parked. > I disagree. All three should be done since the message is still > available for all three actions to be carried out. I'd certainly want > all three to be done if I set them up to be done as such. Well, all three are carried out to the original message. The original message is flagged, and parked. But the copie isn't parked, because at the moment, the coppy was created, the orginal message wasn't parked. >> If this will be realized, it would be good, if TheBat! check (before >> saving the filter) if there are actions after <delete message> and >> <move message> and remind the user that these action will never be >> done: > <delete message> > <run external program> > <play sound> > Are you saying the latter two actions shouldn't be carried out? I > disagree again. Yes, with the my first suggestion, maybe the second is better: >> Another solution would be, that TheBat! move these action at the end >> of the list. So TheBat! would sort: <run external program> <play sound> <delete message> >> mid:[EMAIL PROTECTED] >> mid:[EMAIL PROTECTED] > These bugs are simply bugs that need to be fixed. And how? > They aren't symptoms of filter actions needing to be nullified or > preventing from occurring because of a prior action. I disagree! The filter is: <delete message> <read message> If you run that filter, the message disappear (deleted) and appear again, because its marked as read. There are two possibilitys (which i can imagine) to solve this: Sort <read message> <delete message> and do it in that sequence or ignore the filter options after move or delete message (with a warning, so the user know what has happend) > Crippling filter action sequences is a bad > way of fixing the problem. The problems are made by design - so correct the design, the problems will disappear. > The NFS works the same as MDaemon's filtering system. The actions > are carried out as they're described in the filter rule. The rule > itself, makes it seem to the user that the actions will be carried > out in the sequence described. Then the first sentence is wrong: NFS don't go in the sequence but "random" - in NFS it doesn't matter if you select <delete message> <copy message> or <copy message> <delete message> Or miss I something? -- Regards, Boris Anders, http://www.batboard.de ________________________________________________________ Current beta is 2.13 'Lucky' Beta/6 | 'Using TBBETA' information: http://www.silverstones.com/thebat/TBUDLInfo.html IMPORTANT: To register as a Beta tester, use this link first - http://www.ritlabs.com/en/partners/testers/
