On Sat, Jun 7, 2008 at 7:17 PM, Boyd Collier
<[EMAIL PROTECTED]> wrote:
> Okay; I'm properly chastised for having originally read the documentation
> without as much understanding as I should have. That was a couple of years
> ago, and it worked just as it should have until recently. I've gone ba
Okay; I'm properly chastised for having originally read the
documentation without as much understanding as I should have. That
was a couple of years ago, and it worked just as it should have until
recently. I've gone back through the documentation and now understand
it much better, and I
On Tue, Jun 3, 2008 at 8:40 PM, Boyd Collier
<[EMAIL PROTECTED]> wrote:
> Although everything now works as I think it should, the fact that it didn't
> work correctly when I used Apple's sample code makes me very nervous; have I
> misunderstood something, or... ??
It is an unwritten assumption tha
A couple of months ago, I too had this problem, but didn't
satisfactorily solve it at that time. As my original posting noted,
this change in behavior happened after upgrading to Leopard and Xcode
3.0. The recent posting by Stefan Haller prompted me to spend some
time trying to figure out
Stefan Haller <[EMAIL PROTECTED]> wrote:
> I have an NSDocument-based application that is still pretty close to the
> Xcode template for "Cocoa Document-based application"; i.e. I subclass
> NSDocument but not NSWindowController, and I implement -windowNibName
> but not -makeWindowControllers.
>
I have an NSDocument-based application that is still pretty close to the
Xcode template for "Cocoa Document-based application"; i.e. I subclass
NSDocument but not NSWindowController, and I implement -windowNibName
but not -makeWindowControllers.
When I open a new document, it doesn't cascade; it o
