From: Michael Fisher 
@Date: Mon, 24 Feb 2003 09:25:43 -0800
@Sender: semware-owner{at}sawasdi.apana.org.au



Fred,

>What you say is correct, but I can't do that most of the time.
>If I were to select "Execute" from the menu presented after a
>successful compile, the macro would run against (process) the
>macro's own code itself, which isn't what I need. [..] If I had
>selected "Execute" from the post-compilation message,

Why don't you simply choose "Load" instead of "Execute" from the
dialog shown after a successfull compilation?  This way, the 
newest version of the macro code is in memory, overwriting any 
previous ones, and ready for execution.

If possible, bind the macro to a "throw-away" key-combination
during development, then you can skip that -select part
for executing it.

>I have to select cancel at that menu, then switch to the 
>buffer/file that I want to run the macro against, and then Ctrl-
>X, macroname to >run the macro then.
>Under those circumstances, it seems to be running the loaded
>macro code from the previous compilation.  At least I only get
>good/changed results if I first purge the macro from the
>macro, purge menu.

Really, I *never* have run into the trouble you describe.
Why the complication?  Nothing needs to be purged, just
Edit-Compile-LOAD-Execute.

The only thing that annoys me is that the error message window
can't be closed when you no longer need it.  Otherwise, writing
and testing macros in TSE seems simple and straightforward.

>Hitting cancel and then executing the revised macro

If you hit 'Cancel' the newest, revised macro code is *not* 
loaded, so it cannot be executed either. It seems to me what you 
are purging is the previous, unrevised version still in memory.


--
TSEPro Mailing List
List Maintenance: www.semware.com/html/list.htm



---
[sawasdi.apana.org.au] (3:800/846.13)