You can use BulkLoader to catch your downloaded asset:
http://code.google.com/p/bulk-loader/
L
jonathan howe a écrit :
To put a practical question out about this. I'm setting up something that is
more or less a game with levels. Each level has a different set of
movieclips as its background graphics and enemies for the level.
I store all assets for a single level in an external swf, and using
techniques we've talked about before on the list (swc + getDefinitionByName)
use these assets once they're loaded in via the swf.
The plan was then to dump the assets once the level ends and load a new
level's assets.
The game is small enough that I can conceivably tolerate all level assets
being in memory by the time the game is done. What I need to know is, should
I NOT treat the data as if it's unloaded, given FP9+AS3 behavior? Because
if the player revisits a level, I would normally reload the asset swf for
that level ... now I wonder if that would make a duplicate copy of the
assets in memory? There wouldn't be two copies of the swf's contents in
memory because they'd have identical class definitions... right... or maybe
not?
Now I'm leaning towards an architecture that says: First time you play a
level, load the assets for it, and keep it around always. Next time you play
that level, the assets are already loaded.
-jonathan
On Tue, Apr 15, 2008 at 2:37 PM, Paul Andrews <[EMAIL PROTECTED]> wrote:
I find it rather bizarre that people feel that it's necessary to beat a
drum about this. I doubt that Adobe are sitting back on the issues raised.
The thread has the Air of an hysterical mob. It's amazing how so many
people have produced fantastic systems using Actionscript 3 in spite of the
gloom and doom spouted here.
From what I've read, the FP9 garbage collection is pretty much standard
technology for object based systems - you can't just discard objects that
have references to them. The real problem seems to be related to the other
infrastructure that creates multiple object references that aren't always
removable. I'm not saying bthere isn't a problem, just that it's not worthy
of the histeria being generated. I understand completely it can be a serious
issue for some people.
Anyway, I'll express some faith that Adobe will resolve the issues - I
won't be rolling back to AS2 despite the expert advice of some. I'll consign
a lot of this thread to the same place as the 'end of the world is nigh'
material that those people with placards dispense.
No need to hand me a flaming torch just yet..
----- Original Message ----- From: "Chris Hill" <[EMAIL PROTECTED]>
To: "Flash Coders List" <flashcoders@chattyfig.figleaf.com>
Sent: Tuesday, April 15, 2008 6:40 PM
Subject: Re: [Flashcoders] Is Adobe fixing this big FP9 problem?
ON TOPIC:
I can see that most of us feel very strongly about this bug. Adobe has
made it clear that their formal channel to do something about it is to vote
in their ticketing system for the bug. If there already is a bug, can
someone link to it? Otherwise let's get a bug in there. And then let's vote
for it. I'm pretty sure that based upon the support here we can make this
the #1 bug in their database.
Apologies if someone has already mentioned this. This thread is long and
noisy.
C
_______________________________________________
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
_______________________________________________
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
_______________________________________________
Flashcoders mailing list
Flashcoders@chattyfig.figleaf.com
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
