Quote:
Originally Posted by Toxaris
I will check. It is also a very important setting for me and so far I haven't encountered this. At the moment I am baffled why this could happen, since it will run the rules in sequence. The rules themselves are correct with a description entered? Can you sent me the xml file?
|
Hi, there's little doubt that the rules are 'valid' because:
- If I uncheck the Automate. . . setting, I am asked if I want to apply each rule, I tap 'Y' on every rule, all rules are applied and all replacements happen
- I check the Automate. . . setting, and run the same rule set against the same document as above, some of the replacements don't happen
I have 2 rule sets - in one of them, the much larger one, all the rules have <Permission> set to
false, in the other all the rules have <Permission> set to
true
I am not certain that the same rules are skipped for every document. Before sending you anything I'd like to do some tests to see if there is a pattern as to which rules are skipped, and whether it's consistent across all documents. But I won't be able to do that for a few days.
Curious - why do you use the word
Permission in the XML rule definitions, rather than the word
Confirm.
The latter is used in the 'old' .DOC tables definitions, the documentation, and elsewhere in the add-on, such as in
Automate process S/R rules without 'confirm' flag set.
In non-fiction at least, using different descriptors for the same thing, and the same descriptor for different things is best avoided - some users will find it confusing, and others like me, downright irritating. At school and university I recall my essays getting marked down if/when I did it. But that was before post-modernist rules became de rigueur Ψ²
BR