🚀 go-pugleaf

RetroBBS NetNews Server

Inspired by RockSolid Light RIP Retro Guy

Article View: gnu.epoch.misc
Article #1746

Re: confused by focus policy

#1746
From: Alan M. Carroll
Date: Wed, 16 Oct 1991 15:36
42 lines
2871 bytes
In article <SPOT.91Oct12135519@WOOZLE.GRAPHICS.CS.CMU.EDU>, spot@CS.CMU.EDU (Scott Draves) writes:
> i'm confused by epoch's (3.2, sun4) focus policy.  sometimes when i
> move the mouse from one "screen" to another, the point follows to the
> same screen.  sometimes it doesn't, and i have to click before what i
> type appears in the same window as the mouse.

X maintains a keyboard focus, which determines where keyboard events
go. Epoch has the notion of current screen, which is where Epoch sends
keys, regardless of which screen they actually come from (so, for
instance, if the X focus in on the minibuffer, characters still go
into the current edit screen). When X switches the focus, Focus events
are sent to the affected clients. Epoch provides the events at the
Elisp level, and there is a focus handler that switches the current
screen to the X focus screen, unless the focus screen is the
minibuffer. Because of this, Epoch screens should act just like other
clients. Without knowing the focus policy you've set for your WM, I
can't make any guesses as to what's going on. Various people here run
both pointer and click-to-type focus policies, and have not seen this
problem.

> i spent some time fiddling with this, and it looks like epoch moves
> the point when you enter an epoch screen from another program's window
> (not the root window, however).  but if you switch directly from one
> epoch window to another (they must be overlapping, or just the root
> window intervening), the point doesn't move.

This shouldn't make any difference. Again, the actual behaviour is
controlled by the WM focus policy and the X server. Standard Epoch
should move the current screen coherently with the X focus. What WM
are you using?

> is this a bug or a feature?  i'd prefer the point to follow the mouse
> consistently.

It does for those of us who use pointer focus. Have you made any
changes to the standard configuration? Try typing Control-Z e to see
what handler is dealing with focus events.

-- 
Alan M. Carroll          <-- Another casualty of applied metaphysics
Epoch Development Team   
Urbana Il.               "I hate shopping with the reality-impaired" - Susan
Technical Details
Message-ID: <1991Oct16.153632.30807@m.cs.uiuc.edu>
Path: arc1-ca.pugleaf.net!gmdzi!unido!mcsun!uunet!wupost!m.cs.uiuc.edu!uiucdcs!carroll
References: <SPOT.91Oct12135519@WOOZLE.GRAPHICS.CS.CMU.EDU>

Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit
X-Google-Thread: fc7ee,d878cf8b3919e2c1
X-Google-Attributes: gidfc7ee,public
X-Google-ArrivalTime: 1991-10-17 03:06:02 PST
Path: arc1-ca.pugleaf.net!gmdzi!unido!mcsun!uunet!wupost!m.cs.uiuc.edu!uiucdcs!carroll
From: carroll@cs.uiuc.edu (Alan M. Carroll)
Newsgroups: gnu.epoch.misc
Subject: Re: confused by focus policy
Message-ID: <1991Oct16.153632.30807@m.cs.uiuc.edu>
Date: 16 Oct 91 15:36:32 GMT
References: <SPOT.91Oct12135519@WOOZLE.GRAPHICS.CS.CMU.EDU>
Sender: news@m.cs.uiuc.edu (News Database (admin-Mike Schwager))
Distribution: gnu
Organization: Technophiles Inc. - Engineers with Attitude
Lines: 42