Kali McLaughlin wrote:
>
> Dear list:
> I had been losing about one in 20 emails at the save stage. Thinking it
> was just a corrupt version of Arachne 1.62 I downloaded 1.67, found it
> worked OK and so far has not refused wordwrap.
Hi Kali;
I could be wrong, but I don't think 1.67 is any different from 1.62 in that
area. I'm too lazy to look.:/
> It did however just eat a letter to Sam by throwing up the "save" screen
> and if you do you get the .htm of the email you were replying to.
Michael,
This WILL happen if you are unfortunate enough to TAB out of the textarea or
ESC out and allow the pointer to find a link. It IS a bug, but it is also
a logical problem. How do you decide what the F2 function is going to be
on pages like that ?
What if you REALLY want to save the page HTML (as I do sometimes) ?
You could reverse the logic and say that the HTML save will only work if the
pointer has NOT found a link - and any other time F2 saves the text content.
This would be safer, but you will note that the pointer sits in the lower
right corner of the text window while the window is active. Will this be
considered a link ? It BETTER be for this function.
> OH HELL wordwrap just failed. I find that intensely irritating.
> I will have to go back to using Pegasus which I had been neglecting as this machine
>is fast enought to run
> Insight.
You are probably more correct calling it Outsight. It is part of Arachne,
that you are complaining about, not part of Insight. Insight allows you
to read messages, including what you composed, but the composer is part
of the Arachne editor capability.
So any F2 sensitivity changes will affect all editor usage. Hmmm.
You just pointed out two things. The editor is slow and wordwrap fails.
Maybe I could get interested in that since I can't get the video info
I need. I have written editors in ASM before. <g>
- Clarence Verge
--
- Help stamp out FATWARE. As a start visit: http://home.arachne.cz/
--
