Actually, the output makes perfect sense.
The object foo was only storing a reference to the unnamed function that
traces I still exist.
When you called delete on foo, you only deleted the reference and not the
unnamed function. It is NOT orphaned because you previously assigned bar to
the same
Hey List,
I recently had DropShadowFilters that randomly failed when applied via AS2
to a MovieClip with a BitmapData attached.
It looks like if I had about 4 or 5 BitmapData images attached, one random
MovieClip with the filter wouldn't show anything at all until it was forced
to redraw by
Very slick :)
another quick observation - some items get overlapped
since placement appears random, i can't provide a reliable example
might be a good idea to hide/fade out items that are less than an arbitrary
distance from the viewer's position to avoid this.
On 3/26/07, Wagner Amaral [EMAIL
that's correct - i simply loadclip using the old mc. same code as
adobe's tutorial. but i reiterate - never tried it on a large document
so i dont know if it'll work in your case
On 11/23/06, Tom Shaw [EMAIL PROTECTED] wrote:
I have altered my code but I dont seem to be having much luck.
well darn... i'll make sure i give that a try on monday for my project
as well...
On 11/23/06, Eric_Tibo [EMAIL PROTECTED] wrote:
I'm using this component with no problems...
http://www.digitalflipbook.com/archives/2006/07/flashpaper_comp_3.php
I've set all the possible listeners as in the
I'm facing exactly the same problem developing a content browser
(viewing hundreds of single FP pages) in flash 8... My load times jump
from 300ms to 10 seconds if i try to unloadMovie() first. I haven't
found a solid fix, but I do have a partial workaround - don't unload
the flashpaper. At least
swfdump from swftools (www.swftools.org)
you get output like this
[HEADER]File version: 6
[HEADER]File is zlib compressed. Ratio: 85%
[HEADER]File size: 6389517 (Depacked)
[HEADER]Frame rate: 20.00
[HEADER]Frame count: 52
[HEADER]Movie width:
use a mouse event listener... you'll be glad you did (especially if
you have other buttons on stage)
On 11/8/06, John VanHorn [EMAIL PROTECTED] wrote:
onMouseDown works fine.which got me to thinking that when your on the
root, onMouseDown and onPress are essentially the same event, since
That may be true, but flash and any other program is still limited by
the IEEE floating point specs double precision limits. Flash cannot
internally represent 21 digits without resorting to scientific
notation. If you add a stray '1' to your 21 digit number as the least
significant digit you'll
oops... i forgot to mention (and the above would be confusing
without), 21 digits exceeds the maximum representable in 32 bits
afterwhich flash resorts to floating point. (flash doesnt support
int64 apparently, otherwise you'd have no problems)
On 11/6/06, Merrill, Jason [EMAIL PROTECTED] wrote:
10 matches
Mail list logo
