can the macro command execute an encrypted macro?

speedilad · Post by **speedilad** » Tue Sep 05, 2006 11:38 pm

I have tried to use the macro command within an encrypted macro to execute a macro that is also encrypted. It didn't work...

Is this not possible or am I doing something wrong???

thanks!

Bob Hansen · Post by **Bob Hansen** » Wed Sep 06, 2006 12:53 am

A compiled macro is no different than any other executable file, and can be called in a macro. And the compiled code can call Macro Scheduler command line that executes a macro if Macro Scheduler is installed.

Would be helpful if you include the code in the macros and compiled code that are doing the calling. That should allow us to see the possible cause.

Me_again · Post by **Me_again** » Wed Sep 06, 2006 1:54 am

I think the subject of the question is an encrypted, not compiled macro, and I can't run an encrypted macro from another macro either.

speedilad · Post by **speedilad** » Wed Sep 06, 2006 3:19 am

yes the problem is with an encrypted "not compiled" macro executing another encrypted "not compiled" macro....

thanks!

speedilad · Post by **speedilad** » Wed Sep 06, 2006 3:20 am

the code works perfectly if the macro is not encrypted.

Bob Hansen · Post by **Bob Hansen** » Wed Sep 06, 2006 4:50 am

OOPS!. Sorry, I missed that it was encrypted vs. compiled.

the code works perfectly if the macro is not encrypted.

When which one is not encrypted? The one calling, or the one being called?

speedilad · Post by **speedilad** » Wed Sep 06, 2006 9:33 am

my problem was with a non-encrypted calling an encrypted via macro command.javascript:emoticon('

')
Crying or Very sad

pgriffin · Post by **pgriffin** » Wed Sep 06, 2006 1:43 pm

I can confirm that you cannot use the Macro> command to call an encrypted macro.

What is the reason for encrypting? Maybe Bob was prematurely correct when he mentioned compiled vs encrypted.

With compiled, you could protect the source, but call the macro.

speedilad · Post by **speedilad** » Wed Sep 06, 2006 1:59 pm

the reason is: the script enters a user name and password and I do not have the compiler due to COST

the compiler is only available with the PRO version.

Is the problem with macro execution of an encrypted macro a bug or intentional???

Thanks for all help received!!! Jim

Post by **Marcus Tettmar** » Wed Sep 06, 2006 3:10 pm

This is intentional - the macro command calls an external file and therefore does not know about encryption. Encryption only works for macros run from the Macro Scheduler interface. I can think of a couple of workarounds:

1) Call the encrypted macro like this:

Let>RP_WAIT=1
Run>c:\...\msched.exe ecrypted_macr_name

Replace ... with the path to the Macro Scheduler executable.

2) Assign the encrypted macro a hotkey (Macro Properties/HotKeys). Then have the calling macro issue that hot key, e.g.:

Press Ctrl
Press F5
Release Ctrl

You'll need to add some way to ensure it waits for the macro to complete.

speedilad · Post by **speedilad** » Wed Sep 06, 2006 8:17 pm

thank you!

Let>RP_WAIT=1
Run>c:\...\msched.exe macro2

this solution worked - macro1 ran encrypted macro2