Anthony Martin <amartin_at_engr.csulb.edu> writes:
> On 3 Dec 1997, Brady Montz wrote:
>
> > Anthony Martin <amartin_at_engr.csulb.edu> writes:
> >
> > > On Tue, 2 Dec 1997, Jakob Ess wrote:
> > >
> > > I think this is a bug with FvwmIconMan rather than with CleverPlacement
> > > (SmartPlacementIsReallySmart). There are some flags which must be set on
> > > windows so that their state is known. i.e. are they visible, iconified,
> > > unmapped, etc. CleverPlacement must know if a window is iconified or
> > > unmapped so it knows how to handle it. I believe that FvwmIconMan is
> > > setting the ICONIFIED and/or ICON_UNMAPPED flags wrong, so
> > > CleverPlacement believes that the window isn't actually there.
> > >
> > > I may be wrong, but perhaps the maintainer of FvwmIconMan can take a look
> > > at this?
> >
> > Where are these flags? All FvwmIconMan does is call XMapWindow. Fvwm
> > should be able to figure out the iconified status of the FvwmIconMan
> > windows without any more than that.
>
> I'm not sure who is responsible for setting these flags, but when
> CleverPlacement is trying to figure out the state of I window, I have
> tests such as if(window->flags & ICONIFIED) and if(!(window->flags &
> ICON_UNMAPPED)) to determine the status of the window. For some reason, I
> think the FvwmIconMan window has bogus values for these flags.
> It has been a few months since I looked at this code, and perhaps it is
> something else, but if I remember correctly this is what is confusing
> CleverPlacement.
>
> Tony.
>
Well, those are just internal flags in fvwm. It's responsible for making sure
they are correct.
--
Brady Montz
bradym_at_cs.arizona.edu
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Thu Dec 04 1997 - 16:22:09 GMT