From: "Carlo Hogeveen" 
@Date: Tue, 21 Jan 2003 15:06:45 +0100
@Sender: semware-owner{at}sawasdi.apana.org.au




No, then the compiler generates an error. It is a choice again. Semware was
of the opinion, that it was better to forbid duplicate definitions, then to
let one override the other. In hindsight I would prefer the last definition
to override previous ones, and let the compiler generate only a warning. In
hindsight again, the same would have benifited key definitions too, which we
can currently redifine in the same macro, but in the wrong order: now we
have to put in extra forward declarations. It is an imperfect world, let's
reboot it.

Carlo



-----Original Message-----
From: tsepro-bounce{at}freelists.org [mailto:tsepro-bounce{at}freelists.org]On
Behalf Of Dalton Spence
Sent: dinsdag 21 januari 2003 7:00
To: tsepro{at}freelists.org
Subject: [TSEPro] Re: Overiding UI Menus

> ----- Original Message -----
> -----Original Message-----
> From: Dalton Spence
> Sent: zondag 19 januari 2003 10:37
>
> As Sammy said, good work! However, you didn't carry the concept to it's
> ultimate conclusion; the user interface *shell*. Basically, rather than
> compiling a macro to stick on the autoload list, you rename the source
> "..\ui\My.ui", change the include to "tse.ui", and
compile it from the
> editor. Next time you load the program, the new UI is in place. Restoring
> the old UI is even simpler; just recompile the old source from the
editor.
> This saves the autoload list for those procedures that don't need
resources
> from the UI, and leaves the original UI source "virgin".
----- Original Message -----
From: "Carlo Hogeveen" 
Sent: Monday, January 20, 2003 10:08 AM

> You have a point, but my choice was intentional.
> I prioritized a more loosly coupled solution
> above a more resource efficient one.
> The My.ui solution gets burned into TSE's .exe file,
> changing it, the MyUi.s solution does not.
> Granted, a wee point, but it's mine, and I'll stick to it!
> To each their own ultimate solution for world peace.

As you say, to each their own. One thing I'm not clear about. You overide
the key bindings by placing them before the ones in the include file.
Couldn't the same thing be done with altered procedures, menus, key-, help-
and datadefs?


--
TSEPro mailing list



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