Thanks for the response, but... As I understand it, NSMenuValidation is an informal protocol and doesn't have to be declared as implemented; in fact, I can't find a class that does. Maybe I should lose my Obj-C license for asking, but isn't it sufficient that NSObject declares and implements validateMenuItem: to prevent the NSTableView class from throwing an unrecognized selector exception?
And why is the exception only thrown infrequently (and persistently once it starts), when it's normally successfully invoked every time a click on the respective menu? I'm inclined to suspect a mangled object or class descriptor (since I do have C++ code linked into my app); I am doubtful of that diagnosis only because the object & class seem otherwise intact when the problem is occurring. Thanks, Doug K; On Thu, Jan 29, 2009 at 10:50 AM, Andy Lee <[email protected]> wrote: > On Jan 29, 2009, at 10:41 AM, [email protected] wrote: > >> Using the debugger, I've sent respondsToSelector: messages to it with >> selectors of various methods an NSTableView should respond to, and the only >> response that comes back wrong is validateMenuItem: >> > > NSTableView does not implement the NSMenuValidation protocol, thought it > does implement NSUserInterfaceValidations. > > --Andy > > _______________________________________________ Cocoa-dev mailing list ([email protected]) 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]
