From xemacs-m  Wed Feb  5 19:03:01 1997
Received: from CNRI.Reston.VA.US (CNRI.Reston.VA.US [132.151.1.1])
	by xemacs.org (8.8.5/8.8.5) with SMTP id TAA09905
	for <xemacs-beta@xemacs.org>; Wed, 5 Feb 1997 19:03:00 -0600 (CST)
Received: from newcnri.cnri.reston.va.us by CNRI.Reston.VA.US id aa28757;
          5 Feb 97 19:58 EST
Received: from anthem.CNRI.Reston.Va.US by newcnri.CNRI.Reston.Va.US (SMI-8.6/SMI-SVR4)
	id TAA26494; Wed, 5 Feb 1997 19:58:09 -0500
Received: by anthem.CNRI.Reston.Va.US (SMI-8.6/SMI-SVR4)
	id TAA27784; Wed, 5 Feb 1997 19:58:08 -0500
Date: Wed, 5 Feb 1997 19:58:08 -0500
Message-Id: <199702060058.TAA27784@anthem.CNRI.Reston.Va.US>
From: "Barry A. Warsaw" <bwarsaw@CNRI.Reston.VA.US>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: Steven L Baur <steve@miranova.com>
Cc: xemacs-beta@xemacs.org
Subject: Re: Name of `focus-follows-mouse'
References: <199702040556.WAA07410@branagh.ta52.lanl.gov>
	<m2pvyh9jnr.fsf@altair.xemacs.org>
	<199702042037.NAA12497@branagh.ta52.lanl.gov>
	<199702042147.OAA14285@branagh.ta52.lanl.gov>
	<kig3evcgq5g.fsf@jagor.srce.hr>
	<199702042247.RAA21204@anthem.CNRI.Reston.Va.US>
	<m2iv48f3k9.fsf@altair.xemacs.org>
	<199702050503.AAA26671@anthem.CNRI.Reston.Va.US>
	<kigg1zbboex.fsf_-_@jagor.srce.hr>
	<m29152aipo.fsf@altair.xemacs.org>
Reply-To: "Barry A. Warsaw" <bwarsaw@CNRI.Reston.VA.US>
X-Attribution: BAW
X-Oblique-Strategy: Imagine the piece as a set of disconnected events
X-WWW-Homepage: http://www.python.org/~bwarsaw


>>>>> "sb" == Steven L Baur <steve@miranova.com> writes:

    sb> As John Turner has pointed out, there's more to it than that.
    sb> The correct answer may be to have two variables.  One to
    sb> select between locally active -vs- passive input,

I still like keyboard-focus-model, with values 'passive and
'locally-active.  But if you want to use a simple t or nil value, you
might call it input-model-is-locally-active.  Reverse the sense if you
think passive would be more common. :-)
    
    sb> and the other to select more general behavior wrt to
    sb> assumptions made about frame visibility.

Sorry, I re-read John's message and I'm still not clear exactly what
this other variable would control.  I.e. can you write a docstring for
it?  :-)

-Barry

