From: Fred Holmes 
@Date: Thu, 16 Jan 2003 09:03:02 -0500
@Sender: semware-owner{at}sawasdi.apana.org.au



In the discussion of modifications to key assignments and menus, it was 
noted that many such modifications could be made in an autoload macro, 
except that in an instance such as the code for putting the full path of 
the current filename in the Windows title bar, the statement to be modified 
calls other procedures in tse.ui, which can't be referenced in a 
macro.  Sammy noted that if the procedures are declared "public,"
then they 
can be.  However, in the virgin tse.ui, they aren't declared public.  So if 
one needs to use them, one has to modify tse.ui to declare them public, and 
tse.ui is no longer virgin.  Catch22.

Sammy, would it be possible for Semware to publish a virgin tse.ui in which 
all of the procedures are declared public, or, alternatively, in the 
overall editor code make tse.ui (or the active .ui) an added place to 
automatically search for procedures that are not found when a macro is 
loaded or executed?  Presumably that's done when the [autoload] macro is 
compiled, actually, rather than when it is loaded or executed -- or perhaps 
could be.

The advantage of keeping tse.ui virgin, of course, is that you don't have 
to modify an updated one from Semware with all of the customization that 
you have made to the interface -- it's all in separate autoload macro(s).

Thanks,

Fred Holmes

--
TSEPro mailing list



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