Path: utzoo!news-server.csri.toronto.edu!cs.utexas.edu!uunet!shelby!morrow.stanford.edu!morrow!drapeau From: drapeau@sioux.Stanford.EDU (George Drapeau) Newsgroups: comp.windows.x Subject: Question About Poor Interaction Between Mwm and XView Applications Message-ID: Date: 3 Mar 91 23:44:36 GMT Sender: news@morrow.stanford.edu (News Service) Reply-To: drapeau@sioux.stanford.edu Distribution: comp Organization: Interactive Classroom Experiment, Stanford University Lines: 29 My group has written several applications using the XView toolkit. Our applications tend to set up default initial placements for their windows (i.e., they set XV_X and XV_Y attributes). When we run these applications under control of the OPEN LOOK Window Manager (olwm), the placement hints are followed as we would hope -- the applications' windows appear where we specified in the code. However, when we run the same XView-written applications under the control of the Motif Window Manager (mwm), Mwm does not "listen" to the XView applications' placement requests. My question is, whose fault is this and when will it be fixed either by Sun or by the OSF? (yeah right, like that's not too much to ask) I haven't had the chance to look into the source for either of the culprits to see which hints the apps and wm's set and look at, so any help here would be much appreciated. Also, if anybody knows the philosophy behind whatever decisions were made in how to set/take placement requests, I'd love to hear about it. Thanks in advance, George -- ______________________________________________________________________________ George D. Drapeau Internet: drapeau@jessica.stanford.edu Academic Information Resources Stanford University