• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: MyDocument instance variables, dealloc problems
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: MyDocument instance variables, dealloc problems


  • Subject: Re: MyDocument instance variables, dealloc problems
  • From: Mike Abdullah <email@hidden>
  • Date: Mon, 13 Nov 2006 19:31:30 +0000

This may sound crazy, but you haven't set your _possibleColumns variable as static have you? That would explain how things end up pointing at the wrong documents.

Mike.

On 13 Nov 2006, at 05:53, Andrew Madsen wrote:

Mail is doing something weird to me, mixing up message somehow, so this message appeared in a different thread with a different sender and subject in the message list, but when I clicked on it, I saw your reply. Not sure why that's happening, but that's why I didn't see it earlier.

On Nov 12, 2006, at 12:05 PM, Keary Suska wrote:

on 11/11/06 11:28 PM, email@hidden purportedly said:

In a typical document-based application, a new and different window is
created for each "document". This is accomplished by loading the document
nib. Therefore the outlet for each document *should* be pointing to a new
window.

I realize this, and upon further checking, this is happening correctly. The problem is not in fact that new document instances have docWindow pointing to the wrong place, rather it appears that something (besides me) is messaging the released/dealloced windows from previously closed documents. Again, this only happens if possibleColumns was set in a previous document.



What are the contents of possibleColumns, more more specifically, what are
the contents of the dict that you are passing to the setter? Simply calling
a method should effect anything that is not explicitly in the code, unless
you are using bindings. This response also applies to below.

possibleColumns (and the dictionary passed to the setter method) is a dictionary containing NSTableColumn objects. The key for each object is simply the identifier string for that table column. This is just to make accessing particular columns from the dictionary easy.




Best,

Keary Suska
Esoteritech, Inc.
"Demystifying technology for your home or business"


_______________________________________________ Do not post admin requests to the list. They will be ignored. Cocoa-dev mailing list (email@hidden) Help/Unsubscribe/Update your

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
40gmail.com


This email sent to email@hidden

_______________________________________________ Do not post admin requests to the list. They will be ignored. Cocoa-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
References: 
 >Re: MyDocument instance variables, dealloc problems (From: Andrew Madsen <email@hidden>)

  • Prev by Date: Serious bug subclassing NSTextStorage
  • Next by Date: Document Bundles opening contents
  • Previous by thread: Re: MyDocument instance variables, dealloc problems
  • Next by thread: Apple Help Viewer and/or Apple Help Indexer problems
  • Index(es):
    • Date
    • Thread