While maintaining some older Obj-C++ code I ran into the following
issue: typedef'ed pointer/object types break bindings in Objective-C.
To illustrate, the model code is similar to this:
Model.mm
========
#import <Cocoa/Cocoa.h>
typedef NSString MyString;
@interface Model : NSObject {
MyString *text;
}
@end
@implementation Model
- (MyString *)text { return @"testing"; }
@end
++++++++
In IB the value binding of an NSTextField is connected to the Model's
'text' property. This works as expected when the code is compiled as
Objective-C++. Changing to Objective-C still compiles perfectly, but
when the application starts an exception is thrown inside -[Model
valueForUndefinedKey:]. This puzzled me, and it took me a while to
realize that the typedef seemed to be causing this behavior.
Notes:
-) I'm running Mac OS X 10.5.4
-) typedefed ints, floats, etc. work, obviously.
-) -[Model respondsToSelector:@selector(text)] always returns YES,
even when -[Model valueForKey:@"text"] fails.
Should I have expected this?
patrick
--
Patrick Machielse
Hieper Software
http://www.hieper.nl
[EMAIL PROTECTED]
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
