#1
|
|||
|
|||
Nesting Process Files Action
I tried to nest two process files actions.
I know that this is not possible according to the help, but I think that this is just a problem of implementation: Process files A . Set macro FILE1 = PROCFILES_FULLPATH . Process files B . Set macro FILE2 = PROCFILES_FULLPATH This partly works. For the second FILE1, it will have the correct file name, but the folder of the process files B action. In my opinion there should not be a problem nesting two process files actions if the script implementer takes care of saving the temporary PROCFILES_* macros, so I consider this as some kind of bug, at least a missing feature :-) |
#2
|
|||
|
|||
What's a workaround for nested Processed Files?
it is so true how you described this problem.
The problem is with the PROCFILES_FULLPATH macro which does not get updated properly on the second round in netsed Processed Files. I know it is not recommended to have nested Processed Files. Kinook, what's a workaround for this? I need to Process files, find a file then process another folder and find some files based on the first search. In ohter words something like two loops. Any ideas? thank you |
#3
|
|||
|
|||
For one of the loops, store the filenames in a macro and use a repeating build rule to iterate.
http://www.kinook.com/VisBuildPro/Ma...scriptloop.htm Or put the inner loop in another .bld file and call it with the VisBuildPro Project action. http://www.kinook.com/VisBuildPro/Ma...projaction.htm |
#4
|
|||
|
|||
Nesting is supported in v8.0.
|
Thread Tools | |
Display Modes | Rate This Thread |
|
|