Hi

I understand the PlayMacro is used to run another Macro. Seems like the other Macros must be included within the driver Macro.

Can they be used by pointing to them like this?


ie.

PlayMacro 1 "C:\UB Fix Macros\UB Fix 01.MAC"

Many thanks
Dave

Hi Dave,

why do you need this ?
You can automatically load a macro file (including as many macros as you want) on startup. (see marco-menu, "automatically load" or something)
Sorry, I use german version, so it might be called another way.

--> so you can assemble you macro-sets together as you want and just play them...

rds Bego

Hi Bego

Thanks for the reply. I know about the autoload function. I did not know it could handle more than one at a time. The Macro language gives the ability to call or trigger one or more Macros using PlayMacro. Seems like in order to use this the Macros need to be within the driving Macro. Why do they have to be within the Macro? Why can't we trigger them by pointing to them on the drive?

The autoload would handle the situations where every module is going to use the Macros being triggered but I have situations where I want to use Macros based on the module itself.


Also I notice the Macros take a long time to run. Part of this is based on the large number of find & replace's ( several thousand ) as well as the backup file being created. Any ideas on how to speed up a macro?

Thanks
Dave

Hi Dave,

Well, I think that the "architecture" right now is ok ! Don't confuse a mac-FILE (which you can autoload) with MACROS.
a mac-file holds a set of macros, which can call each other.
So normally, you have 1 mac files and say, 20 macros INSIDE.
Switching between mac files can be done via different uedit.ini files holding different entries for autoload., but this was just by the way.
--> I dont see any necessarity for calling file based macros. you only might run in path-troubles...
Speeding up acn only be done by optimizing code. no "compiler" or something here.

Bego