On Sat, Jun 21, 2025 at 07:24:33PM +0100, Thomas Adam wrote:
> I was doing some digging, and noticed the following check in fvwm/fvwm,c which
> enabled a bugopts workaround for raising clients:
> 
> "Hummingbird Communications Ltd."
> "Network Computing Devices Inc."
> "WRQ, Inc."
> 
> If we detect the above XServers, we enable this workaround, which appears
> here:
> 
> https://github.com/fvwmorg/fvwm3/blob/6000175467fada5d5329f2ecf9e1c0b99937b3ce/fvwm/stack.c#L1038

This was possibly a fix for bug report #232.  See the attached
text file of the bug repot.

Unfortunately the cvs server is gone, so I can't look up which
commit added it.  Is there any git copy of 2.4 floating around?

Ciao

Dominik ^_^  ^_^

-- 

Dominik Vogt
From pater...@ghg.net  Tue Mar  9 15:30:21 1999
Received: from localhost (localhost [127.0.0.1])
        by larry.math.uh.edu (8.9.1/8.9.1) with ESMTP id PAA09036
        for <fvwm-...@fvwm.math.uh.edu>; Tue, 9 Mar 1999 15:30:20 -0600 (CST)
Date: Tue, 9 Mar 1999 15:30:20 -0600 (CST)
From: pater...@ghg.net
Message-Id: <199903092130.paa09...@larry.math.uh.edu>
To: fvwm-...@larry.math.uh.edu
Subject: FVWM2 interaction with PCXware

Full_Name: Mark Paterson
Version: 2.1.7, 2.2
CVS_Date: 
OS: Digital Unix 4.0D
X_Server: PCXWare
Submission from: (NULL) (141.205.2.73)


We are running fvwm on top of PCXWare on Windows NT. Sigh.
With fvwm 2.1.5 and earlier, fvwm windows could be raised above the native
NT
windows. With 2.1.7 and 2.2 (we think 2.1.7 and on, but this is all we have
tested),
this functionality does not work.
Wed Mar 10 12:37:02 1999        drbob   sent reply 1
Thu Mar 11 04:03:08 1999        domivogt        moved from incoming to in 
progress
Mon Apr 12 10:58:20 1999        clasen  changed notes
Sat Apr 17 17:22:54 1999        clasen  moved from in progress to verify fix
Thu Sep  2 19:12:49 1999        domivogt        moved from verify fix to fixed
Mon Apr 12 10:58:20 1999        clasen  The current CVS version now has a fix 
for
this which
triggers only for the Hummingbird Exceed X Server. 
We need the ServerVendor id (eg xdpyinfo output) for 
the server in question to extend the fix. Or maybe
we should apply the fix for all NT-based X servers ? 
From: Bob Woodside <fvwm-...@fvwm.math.uh.edu>
To: pater...@ghg.net
Subject: Re: FVWM2 interaction with PCXware (PR#232)
Date: Wed Mar 10 12:37:02 1999
CC: fvwm-workers@fvwm.org

    Sometime late in the 2.1.x beta phase I put a patch on
my "Unofficial Patches" page that provides an option to
revert to the old handling of the stacking order.

    Unfortunately, I still need to upgrade it for 2.2 -
a last-minute bug fix for the release broke compatibility
with the patch. I'll put up a corrected version this
evening and notify you.

    I wonder if this option is worth adding to the next
release, with a big warning note that its use is *highly*
deprecated, and reintroduces bugs that are long since
fixed...?


- Bob

Reply via email to