> "It all boils down to the point that this little popup that's added to the
> panel to select the file type seems to be screwing everything up."
Is the little popup loaded from a nib?
Is the 'File's Owner' of the little popup's nib set to your document?
Did you know that -awakeFromNib message is
-awakeFromNib is called whenever the receiver is awoken from a nib, or is used
as the owner of a nib that is instantiated. Therefore, it may be called more
than once on any given object.
What's happening:
Document system is preparing an accessory view for the save panel, probably so
it can off
Hi Gregory,
thanks for your support, I was a bit upset because I'm pretty sure the
same instance fails. Because when the crashes began to happen after adding the
second document type, I put a breakpoint in awakeFromNib, and by giving a look
at the document, I knew that this was a documen
Hi Kyle,
the problem is my save panel doesn't have an accessory view :S
Regards.
On Feb 1, 2010, at 6:28 PM, Kyle Sluder wrote:
> On Mon, Feb 1, 2010 at 9:16 AM, Half Activist wrote:
>> Even if i have 10 documents opened, the one that i do a "save as" on has its
>> _instance method_ aw
On Feb 1, 2010, at 12:16 PM, Half Activist wrote:
> I'm not making any assumption on the number of documents that might exist at
> one time.
> Even if i have 10 documents opened, the one that i do a "save as" on has its
> _instance method_ awakeFromNib called a second time:
> The callstack show
On Mon, Feb 1, 2010 at 9:16 AM, Half Activist wrote:
> Even if i have 10 documents opened, the one that i do a "save as" on has its
> _instance method_ awakeFromNib called a second time:
Are you sure it's the same instance? It really looks like you have
accidentally added an NSDocument instance
I'm not making any assumption on the number of documents that might exist at
one time.
Even if i have 10 documents opened, the one that i do a "save as" on has its
_instance method_ awakeFromNib called a second time:
The callstack shows that my document's awakeFromNib is being called during the
Half Activist wrote:
> On Feb 1, 2010, at 8:54 AM, Alexey Zakhlestin wrote:
>
>> On 01.02.2010, at 10:13, Half Activist wrote:
>>
>>> Hello,
>>> In a NSDocument based application, my document class handles 3
>>> different kinds of documents, 1 as a viewer and 2 as an editor.
>>> Actuall
Not at all!
The bug comes from the fact that it is called twice, first when the document's
nib is loaded (and everything is ok) and secondly when the panel opens in which
case yes it crashes becaus e initialization already took place and it shouldn't
be called however.
regards.
On Feb 1, 2010,
On 01.02.2010, at 10:13, Half Activist wrote:
> Hello,
> In a NSDocument based application, my document class handles 3
> different kinds of documents, 1 as a viewer and 2 as an editor.
> Actually, I wished it could handle the 2 types as an editor but here is
> what happens:
>
Hello,
In a NSDocument based application, my document class handles 3
different kinds of documents, 1 as a viewer and 2 as an editor.
Actually, I wished it could handle the 2 types as an editor but here is
what happens:
When I only have 1 type everything is ok as you might
11 matches
Mail list logo
