kdg@world.std.com (Keith D Gregory) (04/01/91)
Two questions about XmBulletinBoard resources in Motif 1.0: 1) allowOverlap: Does this work? It doesn't appear to have any effect on my system. I've tried all sorts of strangeness - unmanaging and then remanaging an overlapping child, after realization, with XtFlushes everywhere. I would assume that the child would not be managed, or its geometry would be changed, but that's not the case. 2) labelFontList (and its ilk): I haven't gotten as crazy trying to make this work -- I've simply set it in the resource file, and noticed that nothing seems to happen with the children. So, what's the story? Are these known bugs in 1.0 that are fixed in 1.1? Or am I doing something wrong? Thanks, -kdg
aw@BAE.BELLCORE.COM (Andrew Wason) (04/02/91)
world!kdg@uunet.uu.net (Keith D Gregory) writes: > 1) allowOverlap: > Does this work? It doesn't appear to have any effect on my system. I've > tried all sorts of strangeness - unmanaging and then remanaging an > overlapping child, after realization, with XtFlushes everywhere. I would > assume that the child would not be managed, or its geometry would be > changed, but that's not the case. If allowOverlap is False, children can overlap - but geometry requests which would result in overlapping children will be denied. So you can create/manage a widget which overlaps other widgets, but you can't change a widgets Position/Dimension which would result in it overlapping another widget. This is what the documentation for allowOverlap implies when it talks about allowing/disallowing "geometry requests" (creating a child widget and managing/unmanaging child widgets aren't considered geometry requests). When allowOverlap is False, BulletinBoard actually forces child widgets to be at least one pixel apart. This seems like an off-by-one bug. Andrew _______________________________________________________________________________ Andrew Wason Bell Communications Research aw@bae.bellcore.com Piscataway, NJ bellcore!bae!aw