Hi, Mark.

When the .toString() or .toSource() method is used on an AEDesc value, the
string data
returned is truncated with an ellipsis, as in:

Me.the_clipboard( 'ustl' ).toString(); // when styled unicode is on the
clipboard
//
//=>
"ustl($000000020000008C000000000000001400000020000000010000000100000000\
xC9$)\x00"

where \xC9 is the MacRoman ellipsis character. The hex codes are cut off after
the 32nd
byte. This is problematic, both in that it means the value cannot be reused with
the .build()
method of AEDescs, and in that a scripter can't work with the data in any other
way, ie: I
tried using the .as() method to get at the data in other ways, but without
success.

So I was thinking that .toString() should be kept as is for simple debugging
purposes, but
that calling .toSource() on an AEDesc should return a complete hex dump.

Just a thought, thanks.

P.S. Am I the only one who is shocked that JSOSA hasn't caught on more in the
Mac
scripting community??? It's such a brilliant language, and Mark's integration
with OSA is so
brilliantly done. So why aren't more people using it???

-- Arthur