As I wrote earlier, there seem to be a few hick-ups with useNetworkmanagement in swfmill... I thought I found a way to have it working, but I have found some weird things.
I use an XML file (with the 'simple' syntax in it) that imports SWFs in the library and place them on the stage. This XML file has <FileAttributes hasMetaData="0" useNetwork="1" /> just after the <movie> tag. In some cases the resulting XML (the one built via the swfmill simplecommand) contains various FileAttributes tags. When all of them have the useNetwork attribute set to 1 everything works fine, but when one of them has useNetwork="0", then the SWF acts like it only has access to the filesystem. I think the topmost FileAttributes tag should overwrite others (they maybe even should be deleted) in order to avoid the oddness I've just mentioned... Anyone out there knows how to fix that? That'd be nice! Quentin. dasp.free.fr On Dec 7, 2007 5:05 PM, Quentin <[EMAIL PROTECTED]> wrote: > Hi there! > I've just found out something weird with network and filesystem access > parameter available in swfmill... > > I was trying to allow my swfs to access the network when executed on the > users' desktop without having the horrible warning. > So I discovered the mighty option ( > http://www.amfphp.org/docs/media/sandbox.gif) > > By reading the list archives I stumbled on these possible ways to set it: > > 1. <FileAttributes hasMetaData="1|0" useNetwork="network|filesystem" > /> > 2. <movie local-access="network"> > > But none of them worked so I went through some swf2xml'd files and I found > out that the only working option is the following : > > <FileAttributes hasMetaData="0" useNetwork="1" /> > > > > placed right after the <movie> tag... > > I hope this helps! > Quentin. > dasp.free.fr > > >
_______________________________________________ swfmill mailing list swfmill@osflash.org http://osflash.org/mailman/listinfo/swfmill_osflash.org
