FVWM Bug Tracking notification
new message incoming/1075
Message summary for PR#1075
From: [EMAIL PROTECTED]
Subject: window focus
Date: Sun, 7 Sep 2003 01:17:21 -0500
0 replies 0 followups
====> ORIGINAL MESSAGE FOLLOWS <====
>From [EMAIL PROTECTED] Sun Sep 07 01:17:22 2003
Received: from lserv00.math.uh.edu ([129.7.128.99])
by util2.math.uh.edu with esmtp (Exim 4.20)
id 19vsrS-00073v-At
for [EMAIL PROTECTED]; Sun, 07 Sep 2003 01:17:22 -0500
Received: from localhost (lserv00.math.uh.edu [127.0.0.1])
by lserv00.math.uh.edu (8.11.6/8.11.1) with ESMTP id h876HLm11838
for <[EMAIL PROTECTED]>; Sun, 7 Sep 2003 01:17:21 -0500
Date: Sun, 7 Sep 2003 01:17:21 -0500
Message-Id: <[EMAIL PROTECTED]>
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: window focus
Full_Name: Aaron Harwood
Version: 2.4.15-1 (fink installed)
CVS_Date:
OS: MacOS 10.2.6
X_Server: XFree86 Version 4.2.99.901 (4.3.0 RC 1) / X Window System
Submission from: (NULL) (128.250.39.70)
Reproducible Problem: Window focus becomes "corrupted". Window "A" is in
front of window "B" on the screen (perhaps completely or partially
obscurring it), however window "B" receives the focus through "A". Even
though for example the cursor is clearly within "A".
To reproduce: start some x terminal windows, say 2, side by side. Start
gvim, by typing gvim in one of the xterms, in such a way that the gvim
window opens and partially obscures one of the xterms. Then reposition the
obscured xterm a little bit (by dragging the title bar). The repositioning
doesn't bring the partially obscurred xterm into the front (it is
repositioned while keeping its order), however fvwm2 will "think" that it
is in the front and will give focus to it through the gvim window, that is
technically incorrect. Repositioning other windows (the other xterm) _will_
bring it into the front. Clicking on the gvim window doesn't change the
circumstance because fvwm2 thinks that it is already in the front. Clicking
on the obscurred xterm brings it into the front and works around the
problem.
A bug fix would be much appreciated. The problem occurs at many different
times (and also occurred with previous fvwm version and previous XFree86
version).
--Aaron
--
Visit the official FVWM web page at <URL:http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm-workers" in the
body of a message to [EMAIL PROTECTED]
To report problems, send mail to [EMAIL PROTECTED]
