• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: does transformedValueClass matter?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: does transformedValueClass matter?


  • Subject: Re: does transformedValueClass matter?
  • From: Matt Neuburg <email@hidden>
  • Date: Thu, 02 Mar 2006 21:46:26 -0800
  • Thread-topic: does transformedValueClass matter?

On or about 3/2/06 9:30 PM, thus spake "Scott Anguish" <email@hidden>:

>
> On Mar 2, 2006, at 11:29 PM, Matt Neuburg wrote:
>
>> Like Tom Harrington in this thread...
>>
>> <http://www.cocoabuilder.com/archive/message/cocoa/2005/11/23/150949>
>>
>> ...I find the documentation on NSValueTransformer's
>> +transformedValueClass
>> bizarre. We are declaring a class, but what class? It is perfectly
>> legal for
>> a reversible transformation to transform a class A object into a
>> class B
>> object and (reversing) a class B object into a class A object, so
>> which
>> should I return from transformedValueClass - A or B?
>>
>
> there is a bug in the current doc (which has been fixed already)
> that says that the transformedValueClass is used in both the
> 'forward' and reverse transformations.. it is actually only used in
> the 'forward' one.

Okay. Tell me more. In the "forward" one, does it represent the class that
transformedValue expects (as input) or the class that it produces (as
output)? Because I would think from the docs that it would be the output,
but the CLStringNumberValueTransformerexample here:

<http://www.cocoalab.com/developer/classes/valuetransformers.htm>
<http://www.cocoalab.com/developer/classes/CLValueTransformers.zip.bin>

...has it the other way around. Yet the example does not break. Meanwhile,
the examples in Examples use NSObject, which is as non-committal as you can
get.

> it is useful information to the runtime

But not useful enough as to affect the functionality of the transformer? m.

--
matt neuburg, phd = email@hidden, http://www.tidbits.com/matt/
pantes anthropoi tou eidenai oregontai phusei
AppleScript: the Definitive Guide - Second Edition!
http://www.amazon.com/gp/product/0596102119
Take Control of Word 2004, Tiger, and more -
http://www.takecontrolbooks.com/tiger-customizing.html
Subscribe to TidBITS! It's free and smart. http://www.tidbits.com/



 _______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden

  • Follow-Ups:
    • Re: does transformedValueClass matter?
      • From: Scott Anguish <email@hidden>
References: 
 >Re: does transformedValueClass matter? (From: Scott Anguish <email@hidden>)

  • Prev by Date: Re: Programmatically setting the value of a bound TextField
  • Next by Date: Re: Eval() ?
  • Previous by thread: Re: does transformedValueClass matter?
  • Next by thread: Re: does transformedValueClass matter?
  • Index(es):
    • Date
    • Thread