Type Method

useStoredAccessor

Returns YES if the stored value methods storedValueForKey: and takeStoredValue:forKey: should use private accessor methods in preference to public accessors.

Declaration

+ (BOOL)useStoredAccessor;

Discussion

Returning NO causes the stored value methods to use the same accessor method or instance variable search order as the corresponding basic key-value coding methods (valueForKey: and takeValue:forKey:). The default implementation returns YES.

Applications should use the valueForKey: and setValue:forKey: methods instead of storedValueForKey: and takeStoredValue:forKey:.

See Also

Deprecated Methods

- handleQueryWithUnboundKey:

Invoked by valueForKey: when it finds no property corresponding to key.

Deprecated
- handleTakeValue:forUnboundKey:

Invoked by takeValue:forKey: when it finds no property binding for key.

Deprecated
- storedValueForKey:

Returns the property identified by a given key.

Deprecated
- takeStoredValue:forKey:

Sets the value of the property identified by a given key.

Deprecated
- takeValuesFromDictionary:

Sets properties of the receiver with values from a given dictionary, using its keys to identify the properties

Deprecated
- takeValue:forKeyPath:

Sets the value for the property identified by keyPath to value.

Deprecated
- takeValue:forKey:

Sets the value for the property identified by key to value.

Deprecated
- unableToSetNilForKey:

Invoked if key is represented by a scalar attribute.

Deprecated
- valuesForKeys:

Returns a dictionary containing as keys the property names in keys, with corresponding values being the corresponding property values.

Deprecated