eric dolecki schrieb:
to remove a movieclip, you need to create or attach it first. if you're
using the IDE to place the mcs, you can't use removeMovieClip().
that is not totally true:
you could always:
var mc = _root.createEmptyMovieClip('___dummy', _root.getNextHighestDepth());
Hello,
While doind some tests, I ran into something that seems a bit weird to me.
On stage I have two movieclips, p1 and p2 and a button, btn.
Each movieclip has a big bitmap (800x600px).
The following code is on frame 1. These are the only things in my app.
Hi,
I am using MediaPlayBack component for my video files so that it can
work on flash player 7.
I have around 30 to 35 flv files and I wanted to use only single
component.
I am trying to change the reference to flv file through url field (URL
to the component) of MediaPlayBack component
and tell me I'm not crazy?
Thanks!
Dimitrios
- Original Message -
From: Dimitrios Bendilas [EMAIL PROTECTED]
To: flashcoders@chattyfig.figleaf.com
Sent: Thursday, August 31, 2006 12:26 PM
Subject: [FlashCoders] Images stay on memory forever?
Hello,
While doind some tests, I ran
Sounds perfectly normal to me, making something invisble in flash doesnt mean it
will unload the content from memory, in fact it doesnt necessarily mean it wont
get rendered.
Im not sure if this is still the case in fp8 but i know that in previous
versions i would also move a clip to
: Thursday, August 31, 2006 7:53 PM
Subject: Re: [FlashCoders] Images stay on memory forever?
Sounds perfectly normal to me, making something invisble in flash doesnt
mean it will unload the content from memory, in fact it doesnt necessarily
mean it wont get rendered.
Im not sure
are the clips created via attachMovie?
why do you need to reclaim 4MB? its not a lot of memory. Flash may well use a
memory management strategy that doesnt require it to immediately return the
memory its allocated.
Dimitrios Bendilas wrote:
Hi Martin,
Ok, but the memory doesn't even free
area.
Does this still make sense? Well, not to me!
Dimitrios
- Original Message -
From: Steven Sacks | BLITZ [EMAIL PROTECTED]
To: Flashcoders mailing list flashcoders@chattyfig.figleaf.com
Sent: Thursday, August 31, 2006 8:32 PM
Subject: RE: [FlashCoders] Images stay on memory forever
: [FlashCoders] Images stay on memory forever?
Setting a movieclip to invisible doesn't free up memory, nor does it
reduce processing power that anything in that clip is doing. The only
thing it frees up is drawing power, which can help in some cases.
The Flash garbage collector is not as good
Message-
From: [EMAIL PROTECTED] [mailto:flashcoders-
[EMAIL PROTECTED] On Behalf Of eric dolecki
Sent: Thursday, August 31, 2006 10:52 AM
To: Flashcoders mailing list
Subject: Re: [FlashCoders] Images stay on memory forever?
to remove a movieclip, you need to create or attach it first
: RE: [FlashCoders] Images stay on memory forever?
That is correct. If you want to remove a movieclip that you did not
attach using attachMovie (one that is manually there on a layer in the
timeline at compile) then you have to first swapDepths() it and then you
can removeMovieClip it.
BLITZ
@chattyfig.figleaf.com
Sent: Thursday, August 31, 2006 9:09 PM
Subject: RE: [FlashCoders] Images stay on memory forever?
That is correct. If you want to remove a movieclip that you did not
attach using attachMovie (one that is manually there on a layer in the
timeline at compile) then you have to first
Message -
From: Steven Sacks | BLITZ [EMAIL PROTECTED]
To: Flashcoders mailing list flashcoders@chattyfig.figleaf.com
Sent: Thursday, August 31, 2006 9:09 PM
Subject: RE: [FlashCoders] Images stay on memory forever?
That is correct. If you want to remove a movieclip that you did not
attach using
Message -
From: eric dolecki [EMAIL PROTECTED]
To: Flashcoders mailing list flashcoders@chattyfig.figleaf.com
Sent: Thursday, August 31, 2006 9:28 PM
Subject: Re: [FlashCoders] Images stay on memory forever?
remove all references to the mc in code see what happens. might not be
immediate
14 matches
Mail list logo
