From: Fred Holmes 
@Date: Mon, 13 Jan 2003 17:10:49 -0500
@Sender: semware-owner{at}sawasdi.apana.org.au



I use an autoload macro that does exactly what you describe, and I leave 
TSE.UI "virgin."  In early days, I would append my custom macro
code to the 
end of TSE.UI (rather than modifying TSE.UI line by line), and it would 
work since the last key definition encountered is the one actually loaded. 
But then I discovered that the same code (simple stuff, such as key 
definitions, pop-up menus, and simple custom procedures) worked just as 
well when loaded as an autoload macro, and it was much simpler that way.

It doesn't work if the autoload macro code calls procs internal to TSE.UI 
that are not regular TSE commands.  For example, if you write the code to 
display the full path of the current file in the title bar.  While I could 
have extracted all of the called code into the autoload macro, it got to be 
too much of a chore before I was finished, so in that case I made the one 
line modification to TSE.UI.  The code for the full path in the title bar 
was provided by Peter Birch, as I recall.

Fred Holmes


At 02:45 PM 1/13/2003, "Hayes Larry Smith"
 wrote:
>Dear Sammy,
>
>In one of your previous comments, you suggested using macro loading when 
>TSE runs rather than messing with the UI file.
>
>Would this work with key definitions too? I have all my function keys 
>redefined to my liking in my current UI file and you inferred that it 
>might be a gotcha when I eventually work with the new TSE GUI UI to keep 
>my current key definitions.
>
>Is there anything special that I should look out for when writing such a 
>pre-loaded macro to redefine the function keys?
>
>Thanks,
>
>HayesGet more from the Web.  FREE MSN Explorer download : 
>http://explorer.msn.com
>
>--
>TSEPro mailing list

--
TSEPro mailing list



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