[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference bulova::decw_jan-89_to_nov-90

Title:DECWINDOWS 26-JAN-89 to 29-NOV-90
Notice:See 1639.0 for VMS V5.3 kit; 2043.0 for 5.4 IFT kit
Moderator:STAR::VATNE
Created:Mon Oct 30 1989
Last Modified:Mon Dec 31 1990
Last Successful Update:Fri Jun 06 1997
Number of topics:3726
Total number of notes:19516

245.0. "Arrows conrol pointer...Why?" by PSG::BUCHANAN (Bat) Fri Feb 17 1989 18:26

Perhaps someone could tell me what I did.

Somehow I lost the usual functionality of the arrow keys and the six keys above
them (Find, Insert Here, etc.).  Insted the arrows controlled the pointer.  In
DCL the arrows could not be used for recalling previous commands and these keys
could not be used in the text editors.  Since I'm new at this I "fixed" it by
using the old tried-and-true method of rebooting the system and they now work
OK.

Anyone seen this before?


T.RTitleUserPersonal
Name
DateLines
245.1Press CTRL/F3 to turn it off againULTRA::WRAYJohn WrayFri Feb 17 1989 18:295
    CTRL/F3 toggles between normal and "mouseless" operation, where
    the cursor keypad duplicates the effect of the mouse.
    
    John

245.2A usability issueSDSVAX::SWEENEYRoads? Where we're going we don't need..roadsFri Feb 17 1989 20:029
    Maybe I should put in a phase 0 request to get a new keystrip legend
    for DECwindows?
    
    What should go on it?
    "Hold Window"
    "Operator Window"
    "Mouse Mode"
    etc.

245.3gotcha!AITG::DERAMODaniel V. {AITG,ZFC}:: D'EramoSat Feb 18 1989 12:516
     Maybe ctrl-F3 should bring up a window telling what it just did,
     how to undo it, and how to customize so that the window doesn't come
     up any more.

     Dan

245.4AGREEDDODO::MARTINFri Apr 28 1989 15:3312
Thanx to this conference I just found out this arrow/pointer problem. I think
.2 is correct in stating a menu should exist to tell them this just happened.
It rendered me and some of my users helpless with WPS-PLUS/VMS which uses these
ten keys.

I have been rebooting all along to cure and never seem to figure a pattern. Now 
I know it would happen when I accidently toggle off OPCOM screen at top.

Thanks,

Ken