Registering a Value Transformer
When creating bindings in Interface Builder, you can specify the name of a value transformer that is used as a “middleman”. In order for your custom value transformer objects to be used in this manner, they must first be registered by name.
Registering a Custom Value Transformer
NSValueTransformer class maintains a mapping of value transformer names, and the corresponding value transformer object. Rather than registering a subclass, individual instances of the
NSValueTransformer subclasses are registered. This allows a value transformer that provides a generalized functionality to be registered multiple times, with different parameters, for different names. For example, you could write a MultiplicationTransformer and specify the number that is used as the multiplier when an instance is initialized. Separate instances could be registered as “MultiplyByTwoTransformer”, “MultiplyByTenTransformer”, and so on.
The example in Listing 1 registers an instances of the Fahrenheit to Celsius value transformer created in “Writing a Custom Value Transformer” using the name “FahrenheitToCelsiusTransformer”.
Listing 1 Registering the Fahrenheit to Celsius value transformer
// create an autoreleased instance of our value transformer
fToCTransformer = [[[FahrenheitToCelsiusTransformer alloc] init]
// register it with the name that we refer to it with
Value transformers are typically registered by an application’s delegate class, in response to receiving a
initialize: class message. This allows registration to occur early in the application startup process, providing access to the value transformers as nib files load.
Availability in Interface Builder
NSValueTransformer subclasses are not automatically listed in the Interface Builder bindings inspector. When inspecting a binding you can enter the name that the value transformer is registered with, but the functionality will not be present in Interface Builder’s test mode. When your application is compiled and run the transformer will be used.