I know the code here is very redundant
but you will really appreciate
it when you have to step through and
debug it like I have for every
little special case that I didn't think of.
I know what you are thinking,
"Why am I here?"
No? Then you must be thinking
"Why do we call this function
twice in a row?"
Programming without a regular expression
recognizer - what a pain. Think
about how much time, space and effort we
would have saved if early on
someone had implemented one. Here endth
/* Hey you think this is ugly you are just
lucky I didn't use a finite
* state machine and use a bunch of goto's */
<<<<<<<<<<<<<<<< WARNING!! >>>>>>>>>>>>>>>>>>>>>>>>>
Fudge mountain ahead.
/* !!!!***%&&%%(() DIRE WARNING %$%&%&%$#"#$"#$***!!!! */
/* IgNorE tHiS aT YouR pERiL */
/* THIS VERSION IS FOR IBM PC CHARACTER */
/* SET ONLY! IT IS REALLY */
/* QUITE DREADFULLY CHARACTER SET AND COMPILER DEPENDENT */
* Just when you thought this code couldn't get any worse....
* Believe it or not, the Routine member is used for not one, not
* two, but FOUR diffrent things!!!
* Can you guess who is responsible for
* this mess? "JW", that's who. If you know who he is, beat him
* up a bit, okay?
* DISCLAIMER: *I* didn't make it this way - I'm just trying to
* cope with it... :-P
/* 17Jun95 - Put your finger in the dike and stop
the leakage */
I know this looks hideous and it
may be hiding some bugs in the define code but
been there, done that
Anyway, it doesn't look
like a bug to me
* The plan is to fudge this for now and when KA gets the
* list part of the adlists working this problem will be
* properly. If you are reading this past the year 1995,
* things have gone a bit slow.
Fudge on top of fudge here. The users
now want to go from having their selected bar from
being at the bottom of their narrow list when they
exit a wide list to being in the middle. I add in
the code below and low and behold if we when we
draw small thumbnails we don't get BarsInMenu = 2
when in reality it should be three and yet we some
how manage to get three on the screen by some bug
further along. Thus I have taken out the next line
of code and thoroughly tested menus with more than
one column and with only one column and everything
seems OK. But then, if you are reading this, all
is probably not fine and I have erred.
if we leave these numbers as is, the bottom of the page
is outside of our little box like a child with their
crayons and Mr. Customer won't like it.
Look, if we get here things are really fubar.
* I have decided to error on the side of caution and leave this
* out until a complete analysis is done (i.e. Never )*/
* Apparently a call to this functions is a "good" idea. I
* don't really understand why...
<In Comms code...>
/* The arrogant pig-dog host thinks we will clear the
/* whenever it tells us to! Ha!
<a comment from the infamous "Hackermann" - probably responsible for
more globals in the code than the rest of the company put together>
* Please do not go around setting *
* global varialbles as you please, This caused *
* the last take in an ad list to be set to the *
* take selected. Resulting in corruption and *
* death. The Gods may forgive you but I never will *
/*Replacement for scrolling function which didn't work, kept blanking
the screen, and crashed every time you told it to scroll a number other
zero. Useful, huh? */
/* I don't think this really works anyway, but I'll
* keep it as is for the moment */
I freely admit I don't know _what_ is going on here...
<and my personal favourite...>
This is a cretinous hack (and yes, that makes me a cretin, I