Re: Release vs. Completed App
Re: Release vs. Completed App
- Subject: Re: Release vs. Completed App
- From: Gordon Apple <email@hidden>
- Date: Sat, 07 Nov 2009 12:04:06 -0600
- Thread-topic: Release vs. Completed App
Thanks. That helped.
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?
On 11/6/09 11:15 AM, "John Terranova" <email@hidden> wrote:
> After you launch your app on its own, go to Xcode and "attach" Xcode
> to your app. "Attach to Process" is in the Run menu. I'm not sure how
> Xcode knows where to find debugging symbols and source code or what
> build settings you need. But, Attach to Process is the way to debug a
> program not running under Xcode.
>
> Good luck,
>
> john
>
> On Nov 6, 2009, at 9:03 AM, Gordon Apple wrote:
>
>> After two years of development, running under Xcode, I'm trying to
>> produce
>> an independently running application for beta testing.
>> Unfortunately, I
>> guess I was naïve to thing that the Release mode in Xcode produces
>> what I
>> need. The app compiles and runs properly under Xcode in Release mode.
>> However, double clicking the produced application itself results in
>> something that runs, but exhibits a multitude of problems, not the
>> least of
>> which is that it won't open a new document when launched. (It will
>> open an
>> existing file.) There are other issues, such as camera video inputs
>> not
>> working at all. I understand that this is a broad question. Since
>> I don't
>> know how to debug something not running in Xcode, where do I start?
>>
>>
>> _______________________________________________
>> 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
>
_______________________________________________
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