Luigi Castelli

I am rewriting some objects to take advantage of the

I am a little confused about the need to implement the

"getvalueof" and "setvalueof" methods. To my

understanding those are methods that are to be used in

objects written using the traditional Max interface if

you want them to be Pattr-aware. If you use the obex

extension the "getvalueof" and "setvalueof" methods

------------------------------------------------------------

THIS E-MAIL MESSAGE IS FOR THE SOLE USE OF THE INTENDED RECIPIENT AND MAY CONTAIN CONFIDENTIAL AND/OR PRIVILEGED INFORMATION. ANY UNAUTHORIZED REVIEW, USE, DISCLOSURE OR DISTRIBUTION IS PROHIBITED. IF YOU ARE NOT THE INTENDED RECIPIENT, CONTACT THE SENDER BY E-MAIL AT SUPERBIGIO@YAHOO.COM AND DESTROY ALL COPIES OF THE ORIGINAL MESSAGE. WITHOUT PREJUDICE UCC1-207.

Tired of spam? Yahoo! Mail has the best spam protection around 

I am rewriting some objects to take advantage of the
new obex extension and attributes.

I am a little confused about the need to implement the
"getvalueof" and "setvalueof" methods. To my
understanding those are methods that are to be used in
objects written using the traditional Max interface if
you want them to be Pattr-aware. If you use the obex
extension the "getvalueof" and "setvalueof" methods
are redundant.

------------------------------------------------------------
THIS E-MAIL MESSAGE IS FOR THE SOLE USE OF THE INTENDED RECIPIENT AND MAY CONTAIN CONFIDENTIAL AND/OR PRIVILEGED INFORMATION.  ANY UNAUTHORIZED REVIEW, USE, DISCLOSURE OR DISTRIBUTION IS PROHIBITED.  IF YOU ARE NOT THE INTENDED RECIPIENT, CONTACT THE SENDER BY E-MAIL AT SUPERBIGIO@YAHOO.COM AND DESTROY ALL COPIES OF THE ORIGINAL MESSAGE. WITHOUT PREJUDICE UCC1-207.
------------------------------------------------------------

Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com


obex-and-pattr

Wrong. You need them in both cases. Implementing the object as an 

obex class permits, among other things, the use of attributes.

Am 02.01.2007 um 22:18 schrieb Luigi Castelli:

> I am a little confused about the need to implement the

> "getvalueof" and "setvalueof" methods. To my

> understanding those are methods that are to be used in

> objects written using the traditional Max interface if

> you want them to be Pattr-aware. If you use the obex

> extension the "getvalueof" and "setvalueof" methods

Wrong. You need them in both cases. Implementing the object as an  
obex class permits, among other things, the use of attributes.

> I am a little confused about the need to implement the
> "getvalueof" and "setvalueof" methods. To my
> understanding those are methods that are to be used in
> objects written using the traditional Max interface if
> you want them to be Pattr-aware. If you use the obex
> extension the "getvalueof" and "setvalueof" methods
> are redundant.


obex and pattr