🚀 go-pugleaf

mcvax!ukc!mupsy!liv-cs!sqrkl, Richard K. Lloyd writes >Wishlist for
the next release of UniTerm (2.1a ??) : Please write to me personally
about things like this, I can't promise an answer (I get a hell of a
lot of mail), but I will read it (not that I would normally answer a
letter with such an agressive undertone).  

>2) Double width, single height text on colour monitors.  

If you want to design 6 fonts, three in a 4x4 cell, and the other half
in a 4*2.5 (:-)) cell, your welcome.  Seriously, designing fonts is a
LOT of work and adding more fonts means the program gets larger
(besides I don't have a color monitor to try any color stuff out (not
that it would help, my ST is so old that it's got a GLUE chip that
won't drive a color set properly (not even the joystick port works)).

>3) Faster Tektronix mode.  

The vector
drawing is fast enough for 9600 baud, at least I've never had any
trouble with it. I relize the text mode is slow, but somewhere I have
to draw the line, or else I'll end up reimplenting the whole OS.  

>4) A one-key NO SCROLL key (none of this ALT-Z stuff) - I currently use 
>   INSERT to go in and out of the SLE...this acts as a useful NO SCROLL
>   key.  

If you hold down the <Alternate> key, you've essentially got a one key
NO SCROLL key, anyway in the more recent versions you can actually put
the no-scroll function on any of the programmable keys.

>5) Why does an alert dialog appear if you disable the SLE and then (accident- 
>   ally or deliberately) press the INSERT key ? This rather makes the 'dis- 
>   abling' aspect a bit useless...!  

No it doesn't, you obviously don't understand why it can be disabled...  

>6) Retain the screen display when switching from or to 132 column mode,
>   rather than clearing the screen and homing the cursor. 

Wrong! No VT1XX, VT2XX or VT3XX compatible terminal works this way,
all clear the screen and home the cursor. The command set of D*C
compatible terminals has no provision for dealing with mixed length
lines (I can think of all kind of perversions you would have to deal
with, if you want to have a terminal with this feature).  

>7) Follow this convention for mouse control : 
> If there is keyboard input or serial line activity, leave the mouse 
> switched off UNLESS the mouse is moved (switch it back on again in that 
> case). Use either the standard mouse arrow or an outlined char cell box 
> for the mouse because these are easier to use than the I-bar.  

Too late, it already works this way in the recent versions.  

> If the mouse button is clicked whilst the mouse is on, then the cursor 
> should move to the character cell nearest to the mouse pointer. BUT....  
> listen to the echo from the host after each cursor arrow code is sent - 
> then the cursor can be 'stopped' if it exceeds the selected position 
> (as is the case if there is tabs between the original cursor position and 
> the destination position selected by the mouse).  

And how do you suggest to do this? (It's not so simple as you think it
is...)  There are about as many different ways to postition the
cursor, as there are editors, the way it's implemented now, it works
ok with xedit and with edt (without tabs).


                              Simon Poole
                              Bitnet: K538915@CZHRZU1A
                              UUCP: ...mcvax!cernvax!forty2!poole