|
|
|
|
#1
04-23-2004, 11:47 AM
|
|||
|
|||
|
Problem with 3.5b (parent-child issue)
Given several steps, some of which are nested children of another step, the child steps are performed even if the parent step is NOT CHECKED.
 Is there a way to make this work properly (If the parent is NOT checked, don't perform child steps)? Is this fixed in a newer version? Thank you. EDIT: also, it would be nice if, when the user checked on a child it automatically checked the parent too. What's the point of the parent child if this isn't or cannot be enforced? Last edited by gilc; 04-23-2004 at 11:53 AM. 
|
|
#2
04-24-2004, 06:44 AM
|
|||
|
|||
|
Visual Build Pro has an option that determines whether the 'Include in Build' flag is nested or not (defaulted to on). See this FAQ for more details: http://www.kinook.com/Forum/showthread.php?threadid=220
|
|
#3
04-25-2004, 03:59 PM
|
|||
|
|||
|
There is a gotch here: If there is a build step test for the child step it is parsed whether the "include in build" step is checked or not (on either the parent or the child). The result of this is that if the test references macros, or has side effects, things are likely to go pear shaped.
A work around is to put the child steps in a subroutine. That way they don't get looked at at all if the calling step is not included in the build.
|
 |
|
|
Hybrid Mode
