Path: utzoo!utgpu!watserv1!watmath!att!att!pacbell.com!ucsd!usc!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!dali.cs.montana.edu!milton!wiml From: wiml@milton.u.washington.edu (William Lewis) Newsgroups: comp.sys.next Subject: Re: Outlet to 'global' interface object. Message-ID: <9818@milton.u.washington.edu> Date: 24 Oct 90 04:43:34 GMT References: <406@nwnexus.WA.COM> Organization: University of Washington, Seattle Lines: 26 In article dml@esl.com writes: >In article <406@nwnexus.WA.COM> adonis1@nwnexus.WA.COM (Adonis Corporation ) writes: > I have several nibs, each with a file owner object. I would like each file > owner object to contain an outlet to a single object contained in yet > another nib. However, Interface builder does not seem to allow me > to connect an outlet of an object in one nib to an object in another > nib. > >There are several ways to do this. The most obvious one is ... [stuff deleted] Or, if you load all of the NIB files with owner=NXApp, you can look up the various objects via NXGetNamedObject() (or some similar call). NXApp contains a table somewhere that associates the textual names of all those named objects in your .nib with the actual objects when the .nib is loaded. (Even objects that don't appear in the little .nib window are named; you just have to find the right aspect of the Inspector.) Notice also you can edit the names of the objects, so they don't all have to be named "ByteSwapperInstance" or whatever ... -- wiml@milton.acs.washington.edu Seattle, Washington (William Lewis) | 47 41' 15" N 122 42' 58" W "These 2 cents will cost the net thousands upon thousands of dollars to send everywhere. Are you sure you want to do this?"