HP3000-L Archives

February 2000, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Wirt Atmar <[log in to unmask]>
Reply To:
Date:
Wed, 23 Feb 2000 13:20:29 EST
Content-Type:
text/plain
Parts/Attachments:
text/plain (48 lines)
Ted writes:

> > Windows made a hard
>  > left turn a few years ago and adopted the Macintosh key sequences -- and
>  > the process dropped all of its oddities, the Cntl-Ins, Shift-Ins being
>  > prime
>  > among them. No modern Windows product uses these sequences any longer.
>
>  Every program which I use under Windows, with one obvious exception, does
>  support those.

Supporting "legacy" key sequences is obviously a common event in software
design. Excel supports all of the Lotus 1-2-3 key sequences, although most
people who use Excel don't know that nor use them.

However, as with all unadvertised and undocumented sequences, they will
eventually be dropped, especially if they come into conflict with other uses.


>  > In QCTerm, everything is made to be as simple as it possibly can be --
and
>  > similar as it can be to the other common Windows-based PC programs.
>
>  If shift-insert is not already taken, you could support those two with
ease.
>  If text is selected, inserting a line makes little sense, so ctl-ins would
>  copy.  Shift-ins would paste and we're both happy.
>
> Alternatively, you could say that when "Transmit control characters to host"
>  is on, all the ctl-whatever sequences become alt-whatever.  Then I could
> learn to use alt-c and alt-v and still be able to do what I need to do in an
> efficient manner.

Again, we would never do that. The Alt keys are meant to be used primarily
with the Windows pull-down menu. What we can do however relatively easily --
and completely consistently with the philosophy we've adopted -- is that when
you are in local edit mode, even if you were in "transmit control characters
to the host", the Cntl+C/Cntl+V sequences would work locally on your text, in
word-processor-like mode. Once you returned to an active connection with the
host, the Cntl+C, etc. keys would no longer be processed locally, but
transmitted to the HP3000 for processing there.

QCTerm doesn't work this way right at the moment, but it is an easy change to
make. More importantly, it is a completely consistent extension of the
general design philosophy I outlined last night.

Wirt Atmar

ATOM RSS1 RSS2