|
Hello all, Just to add to Peter's initial suggestions, I'd further add that IF
your script had no "proc" in it, that is, its all inline, then
perhaps you'd want to set the variables first and then do the source of the
script. Instead of doing this (which sets the variable too late): FME_END_TCL source {$(FME_MF_DIR)Test_FME_END.tcl} ;
set myVar $(macroName) you'd do: FME_END_TCL set myVar $(macroName); source
{$(FME_MF_DIR)Test_FME_END.tcl} ; assuming you want to pull the $(macroname" in as a constant.
I'm guessing quotes may be needed around it as well: FME_END_TCL set myVar "$(macroName)";
source {$(FME_MF_DIR)Test_FME_END.tcl} ; or even: FME_END_TCL set myVar {$(macroName)}; source
{$(FME_MF_DIR)Test_FME_END.tcl} ; I think this may resolve the problems you were having – the variable
needs to be “set” before you can “source” in your
script. BTW you can have several FME_END_TCL lines, they are executed in order.
So if its easier to read: FME_END_TCL set parm1 {value1} FME_END_TCL set parm2 {value2} FME_END_TCL source {$(FME_MF_DIR)Test_FME_END.tcl} Enjoy (and I'm pleased to see you're using this functionality -- as a
further aside, the same type of thing can be done in Python in the soon to be
released FME 2006 as well). Dale ---------------------------------------------------------------------- Get the maximum benefit from your FME, FME Objects, or SpatialDirect via our Professional Services team. Visit www.safe.com/services for details. YAHOO! GROUPS LINKS
|
- Re: [fme] Macros, Parameters & FME_END_TCL Dale Lutz
- [fme] Re: Macros, Parameters & FME_END_TCL RichardW
- [fme] Re: Macros, Parameters & FME_END_TCL mark2atsafe
