From: "Sammy Mitchell" 
@Date: Tue, 14 Jan 2003 08:49:30 -0500
@Sender: semware-owner{at}sawasdi.apana.org.au



Hayes Larry Smith said:
>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.

Appending to what Fred said, if you just add things, it
really isn't that big a deal.  You can just add them to the
newest .ui, when it comes out.  The real gotcha is if you
make changes to the .ui file, rather than just adding new
routines and/or key assignments.

In that case, you have to be careful to merge your changes
with the latest .ui file.

And of course, you really do need to use the latest .ui
file, since some of the new features are implemented in the
.ui file, and there are always bug fixes and improvements
that are added.

>Is there anything special that I should look out for when
>writing such a pre-loaded macro to redefine the function
>keys?

As Fred said, the only "gotcha", is if you want to
reference routines defined in the .ui file.  However, in v4,
there is a solution to this.  I'll write it up and send it
as a separate message.

--
Sammy Mitchell

--
TSEPro mailing list



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