The group concept does not work as expected

[kristogar]

When a group A is subjected to a build rule R I expect that every step inside the group will be skipped if the rule evaluates to false. However if a step B in A is also subjected to another build rule S it was observed that step B gets executed (this leeds to problem because the variable that is used to evaluate S is calculated in one of the steps that is skipped because of rule R). There are two suggestions:
1. Make the group concept consistent in the sense that the group can be evaluated as an entitity such that if it is subjected to a build rule that all group element will not even be evaluated when the rule evaluates to false.
2. Make it possible to put any number of build rules as a condition on a step.

Looking at the xml of the bld file that shows this defect it is clear that to solve this issue it would require a serious redesign. I believe however that this would seriously improve the product.

[kinook]

1. If Tools | Application Options | General | Implement nesting of conditional build rules is checked, in the following scenario:

A
--B

step B will only get built if step A and B's build rules both evaluate true. There is a slight twist in that step B's build rule will still be evaluated if A's build rule evaluates false, which can be a problem if B's build rule criteria depends on A (or other steps below it) having been built; that can be worked around [1], and we do have plans to alleviate this in a future release.

2. Using a script expression in the build rule allows for an unlimited number of criteria to be evaluated for the build rule. See the 'build rules' help topic for more details.

[1] http://www.kinook.com/Forum/showthread.php?threadid=947