Re: IB 3.0 plugin & error "NSMapRemove(): attempt to remove notAKeyMarker" when saving NIB
Re: IB 3.0 plugin & error "NSMapRemove(): attempt to remove notAKeyMarker" when saving NIB
- Subject: Re: IB 3.0 plugin & error "NSMapRemove(): attempt to remove notAKeyMarker" when saving NIB
- From: Jens Miltner <email@hidden>
- Date: Fri, 8 Feb 2008 09:08:02 +0100
Am 07.02.2008 um 23:43 schrieb Jonathan Hess:
On Feb 6, 2008, at 1:46 AM, Jens Miltner wrote:
Am 22.11.2007 um 11:27 schrieb Jonathan Hess:
Hey Jens -
I would guess that that is where an exception is being re-raised.
Do you have a break point on just -[NSException raise]? Or do you
have a break point on objc_exception_throw? objc_exception_throw
is the obj-c exception throwing funnel on Leopard.
If you're able to get a backtrace from the real exception source,
perhaps I can give you better information about the cause of the
exception.
Sorry for the delay - somehow your message got burried inside the
depths of my INBOX :(
Anyway, here's the backtrace from the first break at
objc_exception_throw:
#0 0x93d63077 in objc_exception_throw ()
#1 0x9137904b in +[NSException raise:format:arguments:] ()
[snip]
#53 0x92ea7705 in -[NSApplication run] ()
#54 0x92e749ba in NSApplicationMain ()
Does this ring any bells? It seems to point to the connections
being somehow 'invalid', but I have no idea why.
I can reproduce this with two different IB plugins for different
custom view/control classes I have written. In both cases, I just
followed the documentation for creating new IB plugins, but
apparently, something in those classes seems to be not 100%
compatible with IB 3.0?
It even happens when I just create a new window NIB, drag my custom
control into the window and try to save as NIB 2.0.
If it's not something in my code, I'll happily file a bug report,
but I would like to make sure it's not something in my code that
causes this problem first...
Hey Jens -
I don't think there is actually anything wrong with the connections,
IBCountConnectionsForObject isn't recursive, so I think the
backtrace is showing the wrong symbols. What type of object does
your plug-in integrate? Is it by chance an NSControl subclass that
doesn't have an NSCell instance? If not, I think I'll need a radar
with a small version of your plug-in to fix the problem.
I suppose "an NSControl subclass that doesn't have an NSCell instance"
means it doesn't respond or override the -[NSControl cell] selector?
If so, that's true for both control subclasses that create problems
with saving the NIB. Both of them use more than one cell and thus
can't properly return a single cell object...
Sounds like this is a known issue - is it a bug in IB or is it a bug
in the control implementation where I'd need to implement/override
additional methods from NSControl?
If it's the first, are there any workarounds?
Thanks,
</jum>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden