Hi all,
William Stewart wrote:
At some point the host would have to marshall this... So the care
that needs to be taken is this - don't embed pointers in these
structs, but rather have the memory you pass in to the Get/Set
calls be flat and complete. So, in your example above how you have
this is fine (presuming of course that retval is a value not an
address!).
While we are on the subject, here's one I don't remember being
discussed before:
How would the AU / View residing on different machines work with
files?
The file dialog would be showing up on the "View" machine and would
select file(s) the "AU" machine can't access. While for small files
it would be possible to either have the View know what to do or
send/receive a blob to/from the AU, there are cases where this makes
no sense. As a concrete example, audio files being streamed from or to
disk.
--
Plogue Art et Technologie Inc.
Montreal. http://www.plogue.com
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Coreaudio-api mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/coreaudio-api/email@hidden
This email sent to email@hidden