Eric Hermanson wrote:
3. Attempting to access or return a local variable that has not been
initialized (although you may get a segmentation fault instead of a
BAD_ACCESS, I can't remember). For example,
- (BOOL)someMethod
{
BOOL returnValue;
// code in the method that never sets the
On Fri, Sep 4, 2009 at 9:35 AM, Ian Piper wrote:
> I suppose that when I close the window it is released, so when I try to open
> it again there is nothing to open.
Yep. Common pitfall.
> 1. Why does a window default to having this option checked? It seems odd,
> since the auto-generated code se
On Sep 4, 2009, at 09:35, Ian Piper wrote:
I have been putting together a Core Data application that has three
windows. I wanted to control the appearance and disappearance of
these windows during the course of the application, so added menu
items and buttons with the action makeKeyAndOrder
In my experience this can happen for at least 3 reasons.
1. Over-releasing an object, as you state.
2. Sending a message to an object that has already been released (i.e.
deallocated).
3. Attempting to access or return a local variable that has not been
initialized (although you may get a
Hi all,
I have been putting together a Core Data application that has three
windows. I wanted to control the appearance and disappearance of these
windows during the course of the application, so added menu items and
buttons with the action makeKeyAndOrderFront. However, I found that
the
