[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

2546.0. "Input-focus, use something other than MB1?" by SYSTEM::KALUS () Fri Mar 30 1990 04:03

With the standard DECWindows Interface on VMS (5.1), is it possible to use 
something other than MB1 to set input-focus in a window?

I use programs (eg editors) which use the mouse, and using MB1 in the window
to set input-focus also moves the cursor within the window (very frustrating
if you forget and start typing straight away).

Is it posible to use something like <shift>-MB1 or <ctrl>-MB1 to set 
input-focus? Alternatively, is there a way to stop the mouse-click that 
sets input-focus getting through to the application running in the window?

I've currently got the auto-focus program running, which helps but is not
really what I want.

Chris.
T.RTitleUserPersonal
Name
DateLines
2546.1Try thisAGBEAR::HORNERA.G.Bear, Old fashion teddy bearFri Mar 30 1990 09:307
    Sounds like you use TPU based editors.  Use whatever command is
    appropriate for your editor to enter a TPU command and enter
    SET (MOUSE,OFF).  That will disable the editor's use of the
    mouse.  I've put this in the init routine of my private section
    file to disable it by default.

                Dave
2546.2But I want to use the mouseSYSTEM::KALUSFri Mar 30 1990 10:389
Thanks for the suggestion, but I like using the mouse! (I use DEC EMACS
and explicitly turn the mouse on).

I guess I'm spoilt because I've just come from a UNIX/X11 environment 
where I had full control over the window manager and could set it up 
so it didn't interfere with the applications (eg use <shift>-MB1 to
raise the window). I'd like to do the same sort of thing with DECWindows.

Chris.
2546.3Aim that thing!!TOOLEY::B_WACKERFri Mar 30 1990 12:081
Try ckicking on the title bar instead of the edit window.
2546.4Good luck!BMW320::BERNSTEINIt&#039;s a small planet... RECYCLE!!!Sun Apr 01 1990 12:0715
    If I were .0, I'd be pretty frustrated by all these suggestions. 
    Perhaps mine will be just as inadequate... 8^)
    
    I, too, use autofocus to alleviate this problem somewhat.  Since 
    autofocus has the push/pop buttons defined as f17/f18, I get 
    around it with that, too.  Were you aware of those functions?
    .3's suggestion for AIM is meaningless when a title bar isn't
    visible.  But push/pop may be the thing.
    
    Realizing that that is not the perfect solution, have you looked
    into MOTIF?  With it's AUTOFOCUS functionality, it *AUTOMATICALLY*
    pops that window on top as long as the cursor is over it.  No
    buttons or keys to push... 8^)
    
                                             .steve.
2546.5Input focus "feature" - no title bar darkened.REORG::AITELNever eat a barracuda over 3 lbs.Tue Oct 30 1990 13:4927
    Well, if you want to start from a pause screen, you can get input
    focus in a DECterm window without having the title bar darkened in.
    
    Put the windows you want on your screen - ie do not have them iconized.
    Have the ones you really want to use within view, not overlapping.
    
    Note where your favorite DECterm window is.
    
    Pause your workstation.
    
    Place your pointer over the area where your favorite DECterm window
    is on the screen.
    
    Type in your password.
    
    Type a command.  Voila, it will be taken by the window in which your
    pointer resides.  Move your pointer to another window.  Input focus
    will shift WITHOUT any clicking at all, and without any of the title
    bars being darkened.  However, if you click on ANY menu item, this
    "feature" will be disabled.  I bet that no matter what you do with
    MB1, it will disable this "feature", but I haven't tried everything.
    
    I don't know if this is a bug or a feature.  I'm running VMS V5.3.
    Since I don't usually read this file, perhaps it's already been
    reported....
    
    --Louise