From xemacs-m  Wed Feb  5 00:07:04 1997
Received: from xemacs.cs.uiuc.edu (localhost [127.0.0.1])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id AAA24527;
	Wed, 5 Feb 1997 00:07:02 -0600 (CST)
Message-Id: <199702050607.AAA24527@xemacs.org>
To: bwarsaw@python.org
cc: Steven L Baur <steve@miranova.com>, xemacs-beta@xemacs.org
Subject: Re: Keyboard focus policy (was Re: 19.15b92 - Pure storage exhausted) 
In-reply-to: Your message of "Wed, 05 Feb 1997 00:03:16 EST."
             <199702050503.AAA26671@anthem.CNRI.Reston.Va.US> 
Date: Wed, 05 Feb 1997 00:07:01 -0600
From: Chuck Thompson <cthomp@xemacs.org>

    sb> The XEmacs frame and focus code to me is one big tangled mess
    sb> of seriously broken code.

    BAW> That sucks, but I kind of guessed that.  First we need to
    BAW> agree on the ground rules, and then document what XEmacs
    BAW> *should* be doing in each case.  I hope we can fix XEmacs in
    BAW> this release, but that's my own selfish priority list showing
    BAW> through. :-)


Have fun and be careful.  I'm sure Ben would love to tell you the joys
of trying to make focus work.  You look at it and just see a tangled
mess of broken code and don't have a clue how much effort has been put
in to trying to make it do something sensible.  Getting it right is
incredibly difficult bordering on impossible because X sucks, ICCCM
isn't always clear and no one agrees on what right is.



			-Chuck

