Sorry I should have said a little more about my context.  I'm looking at the 
object passed to the delegate method -control:isValidObject:
Documentation states: "In validating, the delegate should check the value in 
the object parameter…"  I am however unable to assess the value since it is 
being rep'd by an impenetrable class clustered object.

~ Erik


On 2012-07-17, at 5:11 PM, David Duncan <david.dun...@apple.com> wrote:

> On Jul 17, 2012, at 4:58 PM, Erik Stainsby <erik.stain...@roaringsky.ca> 
> wrote:
> 
>> I'm working with the text from a multiline NSTextField. When it arrives in 
>> the delegate it is represented in an NSBigMutableString. Casting this to a 
>> NSAttributedString seems to have no effect on the actual class being used by 
>> the NSString cluster. 
>> 
>> I can't seem to find any documentation on NSBigMutableString.  
>> 
>> Can someone with deep experience tell me if I can _safely_ assume that NSBMS 
>> will respect all of NSAttributedString's method calls ?
>> 
>> Also if I have a convenience function in a category, should I rewrite it as 
>> a category on NSString ? Or directly on the NSBMS, which seems to be a 
>> hidden class? Writing a category on a hidden class just doesn't feel right.
> 
> 
> Your assuming you should care that it is an NSBigMutableString in the first 
> place. From what I can see, the delegates all declare that you are receiving 
> an NSString, and as such you should be treating the value you get as an 
> NSString. 
> --
> David Duncan
> 


_______________________________________________

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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com

This email sent to arch...@mail-archive.com

Reply via email to