Re: FVWM: i can't run fvwm 2.4

From: Gregg Dameron <gregg.dameron_at_lmco.com>
Date: Tue, 10 Sep 2002 16:40:45 -0600

John Latham wrote:

> > Date: Tue, 03 Sep 2002 11:27:37 -0600
> > From: Gregg Dameron <gregg.dameron_at_lmco.com>
> > To: fvwm_at_fvwm.org
>
> > John Latham wrote:
> >
> > > I've just noticed that the one I thought might be the most helpful,
> > > ResizeHintOverride actually is already there in 2.4 -- for some reason I
> > > thought it was only in 2.5. (I am hoping this will help combat the quite
> > > common but appalling 1x1, modal, nonresizable dialog ``feature''!!!!)
> >
> > If a solution to the 1x1 presents itself, please post it. We've been fighting this
> > one in 2.4.7 (and prior to that, under fvwm95 for many years). It seems to happen
> > more frequently if the CPU is under load.
> >
> > Gregg Dameron
>
> Success -- I just managed it!!!!!!!
>
> I have in the last day or so started to build up a set of togglable java bug
> work arounds to put on the menu in AnotherLevelUp. This allows the user to
> switch them on/off at will in a persistent way (i.e. next start/restart has
> them on/off as you last left them). This reduces the risk of unforseen side
> effects, if they were enabled for everyone all the time, and allows users to
> experiment and report back what works, how and when.
>

Thanks for your post, John - please excuse my delay in responding.

Strangely, our 1x1 dialog problem is not Java related. It's happening on dialogs
created by XmCreateMessageDialog() in C code. As I mentioned, it's more likely to occur
when the CPU is under load and/or the X server has a backlog of events to work through
due to being swapped out. Our workaround is to add a map callback for the dialog; when
it fires, we see if the dialog was mapped "too small" and if so, allow the dialog shell
to become resizeable (we are also looking at a programmatic forced resize to a hardwired
height and width).

My suspicion is that both your problem and ours have the same root cause, but at this
point I can't be sure whether it's an fvwm problem or an X server problem. (We run
2.4.7 on Solaris 8 now; previously we ran fvwm95 on Solaris 7.)

I'd be curious to know if anyone else has seen the 1x1 problem outside of Java.

Gregg Dameron


--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Tue Sep 10 2002 - 19:37:35 BST

This archive was generated by hypermail 2.3.0 : Mon Aug 29 2016 - 19:37:53 BST