Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!uwm.edu!bionet!agate!ucbvax!alfalfa.com!nazgul From: nazgul@alfalfa.com (Kee Hinckley) Newsgroups: comp.windows.x.motif Subject: Re: Labels that don't resize when modified [and other stuff] Message-ID: <910320162855.548@alphalpha> Date: 20 Mar 91 21:28:55 GMT References: <9103202033.AA29285@osf.osf.org> Sender: daemon@ucbvax.BERKELEY.EDU Distribution: inet Organization: The Internet Lines: 36 > We would like to fix that in 1.2 and move to a GeometryYes > policy in every manager. However, it may break applications > that have developed Motif subclasses and explicilty > rely on the bogus behavior, for example a subclass of > primitive that would behave differently if the parent > is a BulletinBoard or a Frame. > > if MakeGeometryRequest == Yes > if myparent is a Frame dothis > else myparent is a BBoard dothat > else etc > > That would not work any more. That's fine - that's clearly a broken widget, or at least one which knows that it is dealing with broken widgets and must change when they are fixed. > Any comment on the GeometryYes policy ? Actually I have a number of thoughts about Geometry management in general. Andy Schulert and I are doing a paper for Xhibition which will talk about them and which expresses what we think the Motif widgets should do once they are consistent. Specifically on that question though, I think I would prefer Done instead of Yes. It puts a little more burden on the managers (but not much) and makes life easier for the primitives. It also seems like it's easier to change a widget to that policy than the other, which is good for integrating non-Motif widgets. Why might Yes be preferred? Alfalfa Software, Inc. | Poste: The EMail for Unix nazgul@alfalfa.com | Send Anything... Anywhere 617/646-7703 (voice/fax) | info@alfalfa.com I'm not sure which upsets me more: that people are so unwilling to accept responsibility for their own actions, or that they are so eager to regulate everyone else's.