Mailing Lists: Apple Mailing Lists

Image of Mac OS face in stamp
 
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

User-friendly representation of keyPath expressions for NSPredicateEditor



I'm creating NSPredicateEditor and NSPredicateEditorRowTemplates in code as the key paths for my left-hand expressions are dynamic and not known until run time. The row template is made using an array of key path expressions that look like:

[NSExpression expressionForKeyPath:[... lookup to get dynamic keypath string here ...]]

The new NSPredicateEditor view is a convenience dream, and the app works beautifully, but the left PopUpButton button that is rendered in the NSPredicateEditor view contains the literal key path "someKeyPath". In IB, it's easy to double-click on the pop-up button in the row template and provide a user-friendly substitution like "Not A Key Path Accessor".

Is there an efficient way to do this in code when I'm creating my row templates, or should I be subclassing NSPredicateEditorRowTemplate to override templateViews?

Many thanks,
Jarret
_______________________________________________

Cocoa-dev mailing list (email@hidden)

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/email@hidden

This email sent to email@hidden


Visit the Apple Store online or at retail locations.
1-800-MY-APPLE

Contact Apple | Terms of Use | Privacy Policy

Copyright © 2007 Apple Inc. All rights reserved.