[futurebasic] Re: Break ... Until

Message: < previous - next > : Reply : Subscribe : Cleanse
Home   : December 1997 : Group Archive : Group : All Groups

From: tedd <tedd@...>
Date: Wed, 31 Dec 1997 09:54:09 -0500
Rick wrote:

>My point was not about the _user's_ experience--I certainly wouldn't
>sacrifice the UIF guidelines to make my life as a programmer easier
>(unless I was hitting a deadline :-)).  My point was about the
>_programmer's_ experience--that the
>"single-event-loop-that-calls-everything-else" model is not _always_ the
>best way to implement a standard, event-driven, Macintosh-style program.
>- Rick

Well... it sounds like your program is doing well with two (or more) event
loops and you can handle it. You're a better programmer than I. Whenever I
use more than one event loop, I always have problems down-the-line in
documenting; debugging; or reviewing/editing the code a year later.

It just seems simpler to me to have one event loop going and to organize
things into sets of operations. From viewing program flow in PG Pro during
debugging, I began to have an appreciation of how to get the one event
thing going smoothly. The idea that the flow can travel from one include
file to another without taking much effort while being available for each
include file based upon the status of some global makes perfect sense to me.

Take gLongAction& for example. If the program is on it's first "run" (the
first loop of the event thing), gLongAction& will be flagged (equal to
_mstart) and one can divert the program flow into an initialization include
file to initialize all your variables. In the remainder of the program, the
flow will never again be diverted into the initialization include file. I
like that simplicity.

I found that I can do this with every type of programming problem I've
experienced (Granted my experience may be limited). But, this one-loop
thing allows centralization of things like menu selection, buttons, mouse,
and other operations.

Writing code is similar to any other writing. There is a style and a meter
to all prose and I think we are only discussing variations in the manner.


<mailto:tedd@...>	               http://sperling.com/