From: Fred Holmes 
@Date: Wed, 26 Feb 2003 07:45:23 -0500
@Sender: semware-owner{at}sawasdi.apana.org.au



At 10:55 PM 2/25/2003, DaveG wrote:

>I just received my upgrade to 4.0.  I came across an unexpected question
>during install regarding the Windows UI vs the Classic UI.  I chose classic
>so that I could work with the editor using familiar keystrokes, but I wonder
>if that was the right decision.  The biggest irritation I've had in the past
>is that windows apps use Ctrl-C to copy---horrid in a mixed windows/UNIX
>environment, Ctrl-X to delete, and Ctrl-V to paste.  Ctrl-V in the classic
>UI was the line-draw toggle.  I could really mess up a file in short order
>with Ctrl-V.
>
>So my questions are:  Does the new classic UI still toggle line-draw with
>Ctrl-V? Easy enough for me to answer later.  My main question is would I be
>better off learning the windows UI or stick with the classic UI?  Why?

It would seem to me that the answer is almost entirely a personal one, 
highly dependent upon the way you actually work now.  Keystroke assignments 
are readily changed, to include having them do nothing.  Just create an 
autoload macro and put your new keystroke assignments in them and see how 
they work for you.  In addition to reassigning keys to other functions, 
I've used keystroke assignments to disable keystrokes that I consider 
"dangerous."

For example, in the classic interface, I consider F6 to be too
"dangerous," 
and have put the following into my autoload macro, TSEKEYS.S

         Warn("F6 has been disabled. Use  for
Del to EOL.")

That serves to disable the default key assignment as well as to produce the 
warning.  You could use a message box or whatever as well.

You could do something similar with 

I don't know (haven't looked to see) if there is a complete NOOP command in 
SAL, and I suspect you would have to put something after the keystroke 
statement or the compiler would complain.  If there isn't a NOOP command in 
SAL, Sammy might add one.  Shouldn't be too hard, I think.  Of course, you 
could add your own.  I believe the following would work.

Proc NOOP()
End

In my case I start with the TSE classic interface, and modify from 
there.  Just 'cause that's what I like.  Start with whatever base is 
closest to what you would like.

I've trained myself to use the gray keystrokes in TSE's classic interface 
while using TSE, and Windows stuff in Windows apps.  It comes after a 
while.  In part because I use a distinctive color scheme for TSE, the 
editing window is white on black, just like old DOS.

The new classic interface by default uses Ctrl-V to toggle line draw, but 
perhaps the default font or the font you have chosen is not an OEM font and 
won't actually display the line draw characters.  I don't know what Sammy 
is actually shipping right now.

HTH

Fred Holmes

P.S.  probably isn't all that dangerous now that we have undo.  But I 
used to hit F6 instead of F5 with some regularity when I was in a hurry, 
and then couldn't quickly figure out what I had actually done.  If you 
don't have that problem, they you don't need the keystroke reassignment.

--
TSEPro Mailing List
List Maintenance: www.semware.com/html/list.htm



---
[sawasdi.apana.org.au] (3:800/846.13)