Thanks guys, that was it.
- Walker Argendeli
On Feb 26, 2009, at 4:20 PM, Kyle Sluder wrote:
-doesNotRecognizeSelector: does not throw an exception.
You have a memory management error, and an NSCFType instance is
winding up at the address your window used to be. Have you checked
"Release whe
-doesNotRecognizeSelector: does not throw an exception.
You have a memory management error, and an NSCFType instance is
winding up at the address your window used to be. Have you checked
"Release when closed" in IB?
___
Cocoa-dev mailing list (Cocoa-de
On Wed, Feb 25, 2009 at 5:04 PM, Walker Argendeli
wrote:
> My app has a toolbar, and I recently added a panel. Then, I put a new
> button in the toolbar, and set its action makeKeyAndOrderFront: on the new
> panel. Problem is, the moment I make this connection, the app goes haywire.
> When I la
This is really annoying, because even though I have a symbolic break
point set for objc_exception_throw, I can't get any info.
[Session started at 2009-02-26 16:14:06 -0500.]
2009-02-26 16:14:11.804 MyAppName[2316:10b] *** -[NSCFType
makeKeyAndOrderFront:]: unrecognized selector sent to instan
I've now isolated it to the makeKeyAndOrderFront: method. I tried
just a regular button with that class, but the moment I click it, up
opens the debugger. The toolbar part isn't really an issue. I'm not
really sure what to do from this point, because I can't tell why the
method isn't wor
My app has a toolbar, and I recently added a panel. Then, I put a new
button in the toolbar, and set its action makeKeyAndOrderFront: on the
new panel. Problem is, the moment I make this connection, the app
goes haywire. When I launch the app, both main window and new panel
appear. If I
