1. Bug fix
David Cuny -
I don't understand your fix for the bug in the editor, in your second
message of 9/29/97.
Would you please refile this message, replacing the "alphabet soup" with
plain English?
I wish other subscribers to this Listserv would also keep that admonition in
mind. We aren't all "insiders" like some of you are, or like to think you are.
Wally Riley
wryly at mindspring.com
2. Re: Bug fix
> Would you please refile this message, replacing the "alphabet soup" with
> plain English?
>
> I wish other subscribers to this Listserv would also keep that admonition in
> mind. We aren't all "insiders" like some of you are, or like to think you
are.
Simmer down. There's no need to be insulting. And I'm sure that people would
tone down their level if you politely asked them to.
3. Re: Bug fix
At 06:26 PM 10/1/97 -0400, you wrote:
>---------------------- Information from the mail header -----------------------
>Sender: Euphoria Programming for MS-DOS <EUPHORIA at
>MIAMIU.ACS.MUOHIO.EDU>
>Poster: Cameron Kaiser <spectre at WWW2.BUOY.COM>
>Subject: Re: Bug fix
>-------------------------------------------------------------------------------
>
>> Would you please refile this message, replacing the "alphabet soup" with
>> plain English?
>>
>> I wish other subscribers to this Listserv would also keep that admonition in
>> mind. We aren't all "insiders" like some of you are, or like to think you
> are.
>
>Simmer down. There's no need to be insulting. And I'm sure that people would
>tone down their level if you politely asked them to.
I beg your pardon. I had no intention to insult anyone. Perhaps I should
have included a "smiley" with that message. 
The fact remains, many messages on Listserv are totally obscure to those who
are not "in". They need not be.
Wally Riley
wryly at mindspring.com
>
4. Re: Bug fix
> David Cuny -
>
> I don't understand your fix for the bug in the editor, in your second
> message of 9/29/97.
>
> Would you please refile this message, replacing the "alphabet soup" with
> plain English?
I really do not understand this. When I got the message, it was ONLY a
normal e-mail letter, with the bug fix mentioned in the text lines along
with some other text. An alphabet-soup comes when someone attaches a file
(at least sometimes), and then you will have to decode it manually. I will
paste the text below, so you can see it for yourself:
<Text from David Cuny's letter, repoduced without his permission>
OK, I've found the bug! I'll post it to the web page when it comes back =
on line.
In the mean time, the patch is *very* simple. In the file D_SAVEAS.P, =
line 27 reads:
add_control( 1, SLE, "File &Name:", 2, 14, 32, 14, {} )
It should instead read:
add_control( 1, SLE, "File &Name:", 2, 14, 32, 0, {} )
This sets the DEPTH of the SLE to zero, not 14. The File Name SLE was =
acting like a 14 line MLE, and was receiving the mouse clicks that =
placed the current line to a non-existant line, past the end of the =
sequence. I added the bug some time back when I changed the argument =
order on add_control(). I had fixed the bug, but must have lost it with =
poor version contol between my .P and .E files, so it re-emerged when I =
rebuilt the file.
Again, apologies to all, and I'll post the fix to the fix when Robert's =
Web page comes back on line.
-- David Cuny
<End of Cuny's letter>
Did you get this letter as an alphabet-soup? If so, then there was probably
an error somewhere.
Hope this helps (?)
Einar Mogen
5. Re: Bug fix
>> David Cuny -
>>
>> I don't understand your fix for the bug in the editor, in your second
>> message of 9/29/97.
>>
>> Would you please refile this message, replacing the "alphabet soup"
>> with plain English?
>
>I really do not understand this. When I got the message, it was ONLY a
>normal e-mail letter, with the bug fix mentioned in the text lines
>along with some other text. An alphabet-soup comes when someone attaches
a
>file (at least sometimes), and then you will have to decode it manually.
I
>will paste the text below, so you can see it for yourself:
There was no attached message, as you thought was seen. I assume because
attatched messages are coded into MIME Base 64 or XX or UUencoded, which
use only characters that can be typed using a keyboard without using ALT
or CTRL.
What was meant "alphabet soup", as in just mixed up words to those who
don't understand.
I understood what was meant in both messages, so I'll decode David's fix.
:)
><Text from David Cuny's letter, repoduced without his permission>
And I quoted this stuff without anybodies permission... :)
>OK, I've found the bug! I'll post it to the web page when it comes
>back on line.
>
>In the mean time, the patch is *very* simple. In the file D_SAVEAS.P,
>line 27 reads:
>
> add_control( 1, SLE, "File &Name:", 2, 14, 32, 14, {} )
>
>It should instead read:
>
> add_control( 1, SLE, "File &Name:", 2, 14, 32, 0, {} )
>
>This sets the DEPTH of the SLE to zero, not 14. The File Name SLE was
>acting like a 14 line MLE, and was receiving the mouse clicks that
>placed the current line to a non-existant line, past the end of the
>sequence. I added the bug some time back when I changed the argument
>order on add_control(). I had fixed the bug, but must have lost it
>with poor version contol between my .P and .E files, so it re-emerged
when
>I rebuilt the file.
Ok, he meant the file, D_SAVEAS.E. I guess he got confused with his
preprocessor files. (The preprocessor file that was converted into the .E
file was D_SAVEAS.P... ?)
Change the line 27 to
add_control( 1, SLE, "File &Name:", 2, 14, 0, {} )
An SLE is "Single Line Edit", and MLE is "Multi Line Edit".
I found that I needed to change the 14 to 1 instead of a 0.... Or at
least I think so.... I got an error with 0, but it may have been
something wrong I did and left an EX.ERR earlier (which couldn't be
opened by EE for certain reasons...)
Anyway, if changing the 14 (the second one) to 0 doesn't work, use a 1.
It didn't crash when I used 1 so it is safe... :)
