Article View: comp.sys.next.programmer
Article #1139Re: Getting a PopUpList's window
From: David Griffith
Date: Fri, 14 Aug 1992 13:41
Date: Fri, 14 Aug 1992 13:41
17 lines
1234 bytes
1234 bytes
In article <1992Aug12.002320.2320@afs.com> greg@afs.com writes: > >You are doing an inherently problematic thing, because PopUpLists are NOT >controls, like TextFields and Buttons. They inherit through the Window >hierarchy and are actually subclasses of Menus. By definition, you cannot >ask a Window what Window it lives on. The Matrix lives on the PopUpList, >not the Window it appears to be on, so it's no help either. Even the cover >button is no help, because it's not directly attached to the PopUp. > I think NeXT should implement the concept of parent/child windows to provide a generic solution to this problem (i.e. the PopUpList window becomes the child of the main window). There would probably be many uses for such a feature besides PopUpLists. Also, closing/hiding the parent window could automatically close/hide the children. Dave Griffiths
Technical Details
Message-ID:
<1992Aug14.134143.26334@sinix.UUCP>Path:
arc1-ca.pugleaf.net!sparky!uunet!mcsun!uknet!siesoft!athen!dhgReferences:
<1992Aug12.002320.2320@afs.com>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!mcsun!uknet!siesoft!athen!dhg From: dhg@sinix.UUCP (David Griffith) Newsgroups: comp.sys.next.programmer Subject: Re: Getting a PopUpList's window Message-ID: <1992Aug14.134143.26334@sinix.UUCP> Date: 14 Aug 92 13:41:43 GMT References: <1992Aug12.002320.2320@afs.com> Organization: Primitive Software Ltd. Lines: 17