.ui file upgrade

[Why Tea]

I put all my customization (macros and key definitions) in a .ui file.
While I only need to move those customizations across once for each
new TSE release, it's still not a fun thing to do. I have never looked
into it, does SC support #include files? What is the best practice of
maintaining a customized ui file?

/Why Tea

[knud van eeden]

Possible strategy:
1. Method: Split in changing and non changing parts
Work through your .ui file and split it in parts (manually), once.
Then keep 1 main file, and include the rest of the files.
This is how my main file looks:
--- cut here: begin --------------------------------------------------
// TSE general information (changes)
#INCLUDE ["qedincin.ui"]
// ──────────────────────────────────────────────────────────────────────────────
// my own macros
#INCLUDE ["qedinckn.ui"]
// ──────────────────────────────────────────────────────────────────────────────
// TSE macros
#INCLUDE ["qedincpr.ui"]
// ──────────────────────────────────────────────────────────────────────────────
// TSE menus
#INCLUDE ["qedincme.ui"]
// ──────────────────────────────────────────────────────────────────────────────
// TSE help
#INCLUDE ["qedinche.ui"]
// ──────────────────────────────────────────────────────────────────────────────
// TSE key assignments
#INCLUDE ["qedincke.ui"]
// ──────────────────────────────────────────────────────────────────────────────
--- cut here: end ----------------------------------------------------
So I have 1 main file, and 6 sub (=#include) files.
I only change the 'TSE key assignments' file usually,
then save it,
then load that include file above, and recompile.
with friendly greetings,
Knud van Eeden

/Why Tea

____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now. http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ

[Guy Rouillier]

Also helpful: the sc32 compiler will use the first instance of a
definition and ignore the rest (with warnings about duplicates.) Taking
advantage of this, I put an include for my customizations immediately
after the functions in tse.ui and immediately before "TSE Pull-down
Menus". This allows my key defs to override those supplied by the
standard tse.ui. With this arrangement, the only thing I've had to do
for years is to add one include into the standard tse.ui.

--
Guy Rouillier

[knud van eeden]

> Also helpful: the sc32 compiler will use the first instance of a
> definition and ignore the rest (with warnings about duplicates.) 

> From: Guy Rouillier

Great idea.
 
-It seems thus that one of the simplest methods would be to create a file
with 2 #includes.
-One #include for all your new customizations, the second #include with the old original
 TSE information.

--- cut here: begin --------------------------------------------------

// your own macros and changes
#INCLUDE ["qedincNew.ui"]

// TSE original
#INCLUDE ["qedincOld.ui"]

--- cut here: end ----------------------------------------------------

with friendly greetings,
Knud van Eeden

____________________________________________________________________________________

[Carlo Hogeveen]

A very loosly coupled way to change parts of the User Interface
without changing but still using Semware's .ui files
is demonstrated in the MyUi.zip example on my website:

http://www.xs4all.nl/~hyphen/tse/index.html

-----Original Message-----
From: sem...@googlegroups.com [mailto:sem...@googlegroups.com]On
Behalf Of Why Tea
Sent: zaterdag 26 april 2008 15:29
To: SemWare
Subject: [TSE] .ui file upgrade

[Why Tea]

Thanks to everyone's response. It didn't take long
to make the changes. One more question, how do you deal
with the situation when you have a hook to your macro
that is started up in WhenLoaded()?

On Apr 27, 12:09 pm, "Carlo Hogeveen" <Carlo.Hogev...@xs4all.nl>
wrote:

[Fred Holmes]

I use an autoloaded macro, which I call TSEKEYS.S, which contains all of my keystroke reassignments and "minor" macros. I leave TSE.ui virgin. Works for me.

Fred Holmes

[Phil Kane]

On 4/29/2008 5:15 AM, Fred Holmes wrote:

> I use an autoloaded macro, which I call TSEKEYS.S, which contains all
> of my keystroke reassignments and "minor" macros. I leave TSE.ui
> virgin. Works for me.

I, OTOH, copy tse.ui to tse32.ui and hack away at tse32.ui to my
heart's content - adding an #INCLUDE for a file called PMKSTUFF.INC
which has special macros and adding a section called PMK_KEYS in
tse32.ui redefining keystrokes. I do the same for tse.cfg creating
tse32.cfg. Then I save the "original" e.exe file and burn in the tse32
combinations (.ui and .cfg) as tse32.exe knowing that there's always a
"safety net" available.

--
Phil Kane