Calling /macro from a macro... Ill effects?

cantrememberusername · Post by **cantrememberusername** » Tue Sep 30, 2003 9:49 am

Are there any ill side effects to calling /macro from within a macro?

Doing this reports that the current macro ended and vars are cleared.

Scenario:

Have a macro called test.mac

Last line of test.mac is "/macro test.mac"

will this have any problems?

For those that ask why? Lets just say that test.mac has a tendancy to change frequently from a process outside of macroquest...

MQSEQ · Post by **MQSEQ** » Tue Sep 30, 2003 9:56 am

Create a master macro and then include all the other scripts into the master with the include statement.

This would allow you to call the routines from other scripts.

grimjack · Post by **grimjack** » Tue Sep 30, 2003 10:04 am

MQSEQ wrote:Create a master macro and then include all the other scripts into the master with the include statement.

This would allow you to call the routines from other scripts.

This wouldn't help him if his second macro is being changed or generated dynamicly from another source which is what I think he is hinting at.

I have never had a problem calling a macro from another. It does stop the 1st macro when the second one is ran, however..

Thanks
GrimJack

cantrememberusername · Post by **cantrememberusername** » Tue Sep 30, 2003 10:08 am

Yes, the test.mac is dynamically generated, and I need it to reload itself.

Just wondering if after a few hundred "reloads" by calling itself there might be memory corruption/leaks.

Anyone else successfully attempt something like this?

MQSEQ · Post by **MQSEQ** » Tue Sep 30, 2003 10:10 am

Depends on what actually changes. I guess we need to see what he is wanting to do.

MQ>EQ · Post by **MQ>EQ** » Mon Oct 06, 2003 9:55 pm

why dont u make a hotkey in eq like

/endmacro
/macro test.mac

and put somewer in your script /press 1

MQ>EQ