Also, an unknown to me is what happens when the logic in a NMF set is faulty, say with an infinite loop.
I've seen several actions that can/will delay a rule action. For example, if you set it to play a sound every time a rule action is taken and another when it is not that sound length is added to that of the rule. Another thing to consider is once a rule is satisfied it should exit the rule set or it will go all the way down to the bottom of the rule set doing nothing, or worse, doing wrong.
Considering that a set of rules is executed from top to bottom, I think it is a good idea to create them as subroutines (Labels, preferably commented). This will give the user more control over the actions and will offer him the chance to chain them together to satisfy more complex actions.
Finally, actions such as moving messages to folders, changing colors, statuses, and other parameters are practically instantaneous. Others, such as saving attachments to disk (I use this option frequently), take longer, but are rarely noticed. Another action that has a greater impact on execution time is reading and/or maintaining lists, especially if they are very large. Since these lists are not indexed, their reading, I believe, is also top-down until they are satisfied (or not). I also keep a small window displaying System Messages. It helps me keep track of most actions.
[quote="pid:57707, uid:28772"]Also, an unknown to me is what happens when the logic in a NMF set is faulty, say with an infinite loop.[/quote]
I've seen several actions that can/will delay a rule action. For example, if you set it to play a sound every time a rule action is taken and another when it is not that sound length is added to that of the rule. Another thing to consider is once a rule is satisfied it should exit the rule set or it will go all the way down to the bottom of the rule set doing nothing, or worse, doing wrong.
Considering that a set of rules is executed from top to bottom, I think it is a good idea to create them as subroutines (Labels, preferably commented). This will give the user more control over the actions and will offer him the chance to chain them together to satisfy more complex actions.
Finally, actions such as moving messages to folders, changing colors, statuses, and other parameters are practically instantaneous. Others, such as saving attachments to disk (I use this option frequently), take longer, but are rarely noticed. Another action that has a greater impact on execution time is reading and/or maintaining lists, especially if they are very large. Since these lists are not indexed, their reading, I believe, is also top-down until they are satisfied (or not). I also keep a small window displaying System Messages. It helps me keep track of most actions.
-- Euler
Pegasus Mail 4.81.1154 Windows 7 Ultimate
IERenderer: 2.7.2.8 AttachMenu: 1.0.2.0
PMDebug: 2.5.8.37 BearHTML 4.9.9.6