Need for speed

[kriemer]

I am planning on using WorkFlow Designer as a documentation/Presentation tool for macro development. Not wanting to slow down the execution of my macros I was wondering about best techniques.

I note that I can import previously saved macros into a single "Action Block" of a new macro. This would allow me to repeatably reuse typical archetype macros without reentering code. Does this technique slow down or impact on macro stability?

Thanks

k

[Marcus Tettmar]

For code re-use just use the Include command. So the action block could simply be:

Include>existingscriptfile.scp

The code within the action block will run at the same speed as it would run inside Macro Scheduler.

The only difference is between blocks where in Workflow Designer there is by necessity a tiny, tiny delay introduced in order to show the process proceeding visually. Other than that there is no difference in speed.

[kriemer]

Two remaining questions then:

1- Will the macro still compile with the "Include>existingscriptfile.scp"
2- Is there any difference between "Include>XXX.scp" from "Macro>XXX.scp" in this case?

Thanks

k

[Marcus Tettmar]

1. Yes, you can compile statically or dynamically.
2. See: http://www.mjtnet.com/blog/2009/09/09/i ... ary-files/