Re: Release vs. Completed App (partly solved)
Re: Release vs. Completed App (partly solved)
- Subject: Re: Release vs. Completed App (partly solved)
- From: Gordon Apple <email@hidden>
- Date: Sat, 07 Nov 2009 14:31:33 -0600
- Thread-topic: Release vs. Completed App (partly solved)
It turns out that the doc nib problem was a static text binding that had
not been updated when we changed file owner from doc to windowController.
One problem down -- more to go. I still don't understand why these issues do
not show up under XCode.
On 11/7/09 2:07 PM, "email@hidden"
<email@hidden> wrote:
> Now, taking one problem at a time, the app will not successfully open a
> document when launched without running under Xcode. By process of
> elimination, I have isolated the problem to the main document nib. I have
> carefully eliminated all warning messages related to this nib (running under
> Xcode). This nib has never been a problem running under Xcode. In the
> doc's init, a basic data hierarchy is created, accessible through a single
> root reference. The nib is fairly complex, consisting of four tab views,
> the first of which contains five tab views, each containing a table to
> display the data hierarchy. The window is created as follows:
>
> - (void)makeWindowControllers // Override of NSDocument.
> {
> NSWindowController* courseTreeController =
> [[NSWindowController alloc] initWithWindowNibName:@"RTPDocument"];
> [self addWindowController:courseTreeController];
> }
>
> With a breakpoint on this, it appears that it is creating the nib and
> adding it to the doc's windowControllers (previously nil when it is empty).
> Then, clicking on the apps icon in the doc (no window to click on yet), it
> executes what I assume is a new document default action again, throwing me
> back to the breakpoint and starting over. Note that "self" (i.e., the doc)
> is now different and has nil windowControllers. A new controller is then
> successfully added, and the cycle repeats.
>
> I replaced the RTPDocument nib with a simple window test nib, and it ran
> successfully, which is what leads me to believe the problem relates to the
> RTPDocument nib.
>
> Again, this only happens when running independently, not launched under
> Xcode. Is something, maybe, getting left out in the build for the nib? If
> so, why would it run correctly under Xcode?
--
Gordon Apple
Ed4U
Little Rock, AR
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden