FW: Re: Two EOModels in one project

Correct, there's no PB.project file these days, nor even a *.xcode file, just 
*.xcodeproj.  And I'm using Xcode, not Eclipse/WOLips.

Denise
 -------------- Original message ----------------------
From: Mike Schrag <[email protected]>
> Ah I bet I know what it is ... I bet Xcode doesn't produce the  
> PB.project file anymore.  I use Eclipse w/ WOLips which writes  
> PB.project, xxx.xcode, and xxx.xcodeproj files (for all the various  
> combinations of backwards compatibility).  I'm guessing if you have a  
> PB.project file, then EOModeler will load its data directly from that  
> (like the "old days").  However, if you don't, I have a sneaking  
> suspicion that it uses the same magic communication mechanism that  
> WOB uses to talk to Xcode.  So if you're using WOLips, you can just  
> do this without having any editors open (because it has the  
> PB.project file to load from).
>
> ms
> 
> On Jan 24, 2006, at 9:49 PM, Denise Howard wrote:
> 
> > Thanks very much to all who offered suggestions.  Here is what  
> > finally did the trick to make both EOModels appear in the popup  
> > list of the relationship inspector in EOModeler.  There are two  
> > equally important parts to it, besides them both being in the same  
> > Xcode project:
> >
> > 1. both models must be open, and
> > 2. they must have been opened from within Xcode
> >
> > I think once you've created one cross-model relationship #1 no  
> > longer applies, at least it worked that way for me.
> >
> > Denise