Google Groups Home
Help | Sign in
.ui file upgrade
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  8 messages - Collapse all
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
Why Tea  
View profile
 More options Apr 26, 9:29 am
From: Why Tea <ytl...@gmail.com>
Date: Sat, 26 Apr 2008 06:29:07 -0700 (PDT)
Local: Sat, Apr 26 2008 9:29 am
Subject: .ui file upgrade
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


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
knud van eeden  
View profile
 More options Apr 26, 9:37 am
From: knud van eeden <knud_van_ee...@yahoo.com>
Date: Sat, 26 Apr 2008 06:37:15 -0700 (PDT)
Local: Sat, Apr 26 2008 9:37 am
Subject: Re: [TSE] .ui file upgrade
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


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Guy Rouillier  
View profile
 More options Apr 26, 7:12 pm
From: Guy Rouillier <guyr-...@burntmail.com>
Date: Sat, 26 Apr 2008 19:12:25 -0400
Local: Sat, Apr 26 2008 7:12 pm
Subject: Re: [TSE] Re: .ui file upgrade
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

    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
knud van eeden  
View profile
 More options Apr 27, 4:36 am
From: knud van eeden <knud_van_ee...@yahoo.com>
Date: Sun, 27 Apr 2008 01:36:21 -0700 (PDT)
Local: Sun, Apr 27 2008 4:36 am
Subject: Re: [TSE] Re: .ui file upgrade

> 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

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


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Carlo Hogeveen  
View profile
 More options Apr 27, 6:09 am
From: "Carlo Hogeveen" <Carlo.Hogev...@xs4all.nl>
Date: Sun, 27 Apr 2008 12:09:25 +0200
Local: Sun, Apr 27 2008 6:09 am
Subject: RE: [TSE] .ui file upgrade

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


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Why Tea  
View profile
 More options Apr 29, 4:43 am
From: Why Tea <ytl...@gmail.com>
Date: Tue, 29 Apr 2008 01:43:42 -0700 (PDT)
Local: Tues, Apr 29 2008 4:43 am
Subject: Re: .ui file upgrade
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:


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Fred Holmes  
View profile
 More options Apr 29, 8:15 am
From: Fred Holmes <f...@his.com>
Date: Tue, 29 Apr 2008 08:15:13 -0400
Local: Tues, Apr 29 2008 8:15 am
Subject: Re: [TSE] .ui file upgrade
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

At 09:29 AM 4/26/2008, Why Tea wrote:


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Phil Kane  
View profile
 More options Apr 29, 1:34 pm
From: Phil Kane <p...@kanafi.org>
Date: Tue, 29 Apr 2008 10:34:39 -0700
Local: Tues, Apr 29 2008 1:34 pm
Subject: Re: [TSE] Re: .ui file upgrade
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


    Reply to author    Forward  
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2008 Google