> I’m thinking that I can probably do it at least messily for testing with the 
> shared method descriptorWithDescriptorType, but while that takes a memory 
> block to the data, the type is separate. I don’t know if that means that 
> you’re going to do a coerce on it, or if thats actually the raw data and not 
> the aedesc 8 byte type/handle object that I normally store as an aedesc?

it's just a wrapper. 
Data is copied for reference counting correctly.

> I would like to ultimately use these classes as much as possible as it would 
> be easier to avoid aedesc leaks since I assume they properly kill the desc 
> when they go out of scope otherwise you have to keep track of them manually 
> which is problematic ;)
> 

NSAppleEventDescriptor class should do it right.


Sincerely
Christian

-- 
Read our blog about news on our plugins:

http://www.mbsplugins.de/

_______________________________________________
Mbsplugins_monkeybreadsoftware.info mailing list
[email protected]
https://ml01.ispgateway.de/mailman/listinfo/mbsplugins_monkeybreadsoftware.info

Reply via email to