From xemacs-m  Wed Sep  3 17:53:35 1997
Received: from atreides.eng.mindspring.net (atreides.eng.mindspring.net [207.69.183.11])
	by xemacs.org (8.8.5/8.8.5) with SMTP id RAA28029
	for <xemacs-beta@xemacs.org>; Wed, 3 Sep 1997 17:53:34 -0500 (CDT)
Received: (qmail 27081 invoked by uid 52477); 3 Sep 1997 22:53:05 -0000
To: xemacs-beta@xemacs.org
Subject: Re: XEmacs 19.16-b91 w/ Lesstif 0.80
References: <9709030555.AA02628@salbuild.lehman.com> <m23enm5ap1.fsf@altair.xemacs.org> <86d8mqrrd2.fsf@kramer.in.aventail.com>
Mime-Version: 1.0 (generated by tm-edit 7.108)
Content-Type: text/plain; charset=US-ASCII
From: Sudish Joseph <sj@eng.mindspring.net>
Date: 03 Sep 1997 18:53:05 -0400
In-Reply-To: wmperry@aventail.com's message of "03 Sep 1997 14:59:21 -0700"
Message-ID: <yviaafhurovi.fsf@atreides.eng.mindspring.net>
Lines: 17
X-Mailer: Gnus v5.4.65/XEmacs 20.3(beta19) - "Kiev"

William M Perry writes:
>   And you typically cannot send keyboard events while your mouse is in the
> menubar area, at least under Linux w/MetroX or XFree86

Thanks for isolating the causes of this, it's been driving me nuts.
Actually, what I see is much worse: no keyboard events if the mouse is 
outside of the app window, period.

This might be window manager lossage (I'm using WindowMaker, which I
think William is using as well) in ClickToFocus mode.  I switched to
ClickToFocus and WM primarily because it has better support for
next_window/prev_window from the keyboard than any fvwm derivative,
among other features.  So, the above problem is doubly galling as it
renders the keyboard accelerator useless most of the time.

Off to recompile w/o lesstif,
-Sudish

