We used to use this approach, utilising Object.watch to check for changes - however we started getting the occasional exception - we switched to xml sockets and haven't looked back since.
M > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf > Of Lee McColl-Sylvester > Sent: 24 April 2006 10:27 > To: Flashcoders mailing list > Subject: RE: [Flashcoders] Best practice DLL Integration > > That's a little overkill. What's the point in using > XMLSockets where the data is persisting in one place? It's > better to use SetVariable from the EXE to the Flash movie and > send XML as strings to the variables (which are > getters/setters), and ExternalAPI for Flash to the EXE which > also sends XML. If you look at my blog on my website > (www.designrealm.co.uk) I have a post where I explain a good > way to proxy xml streams from Flash to functions in your EXE; > at least for .NET. It's also just as doable with C++ function > pointers and there are other hacks for other languages. > > Regards, > Lee _______________________________________________ [email protected] To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
