Re:
> THE X-PHILES
...
>      o a left-mouse click, in any QCTerm window, will establish an initial
> cursor point, moving the cursor to that point. Holding the left button down

That's unfortunate.  I'd hoped you'd go with the method I suggested
half a year or so ago:

   1) if the window doesn't have the focus, clicking anywhere in it
      brings the window to focus *WITHOUT* changing the cursor location.

   2) A second click would then change the cursor location.

That's how Reflection 1 works, and how MS Word 2000 works.

Once you try it, you realize: it's the obviously the way to do things.

I urge you to do it right in QCTerm, too :)

I.e.:

   1) first click in a window that doesn't have focus bring the focus to it
      without disturbing the cursor.

   2) second click moves cursor

   ...rest of new copy/paste as described by Wirt.

> After we independently devised, with great pride I might add, this
> X-windows-like copy and paste method, we were surprised to find that some

I'm looking forward to it ...with the above proviso.

> Take a look at the right-click method in Notepad for the slightly alternate

Ironically, NOTEPAD doesn't do the focus/cusor stuff properly.  It uses the
old (pre-awakening) style: the first click brings focus *and* moves the cursor.

> ========================================
>
> While the terminal emulator portion of QCTerm is nice -- and it has to be
> perfect -- it's van Gogh that is the item that will change people's minds
> about the HP3000. A terminal emulator presents a face to the world that lies

Although I can't find a copy, back in July or so I sent you
an important enhancement request for VanGogh.  ... a request
for a facility that may be critical to the programmer's acceptance of VanGogh.

It *NEEDS* an error reporting mechanism.

I've already discovered that it's easy to write incorrect
VanGogh scripts ... and there's no debugging mechanism / error
reporting mechanism.

IIRC, I suggested something like having a new VanGogh directive that
reports the current "worst error" status back to the user, and clears the
error flag.  With such a directive, I could do:

   ...start VanGogh mode...
   ...send some directives...
   ask for error status.  (and clear flag)
   if error then abort.

   ...send some directives...
   ask for error status.  (and clear flag)
   if error then abort.
   ...
   ...trigger VanGogh display.

It would be up to the programmer to decide how frequently ... if at all ...
he/she wanted to get error information.

This is part of the general need that all programming
languages/environments/APIs have ... a need that isn't always addressed:

   1) how do you detect & handle errors;

   2) how do you interrogate the environment.

Clearly, point 2 opens a whole new dialog for QCTerm :)

But...let's focus on point 1 now.

SS
Stan Sieler                                           [log in to unmask]
www.allegro.com/sieler/wanted/index.html          www.allegro.com/sieler