In the end it doesn't even matter?

[Kimchee]

So I am getting tired of using correct programming logic just to get bugs because of flash.

for example, you cant put stage.length or stage.width to get x, y values at the start of a program because the stage's width and length change as the program loads.

Another example is I add mc to a stage and if I goto a different frame and back those mc are gone, but if I got to a different frame and then another one that then redirects me to the first the mc are there as they should be. Strange, strange, strange...

So my question is, are there any other wierd flash bugs that we need to be aware of as programmers, so we don't spend 12 hours debugging something with logic?

[newblack]

it's width and height, not length and width. and the stage's dimensions are representative of what is currently on the display list- so it is completely application specific. if it didn't change, then it would be a bug- not the other way around.

i don't follow what you're saying about MovieClip behavior; sounds weird though.

it's really best to do the work and know that something does NOT behave the way that it should or is documented.

[maskedMan]

Originally Posted by Kimchee

So my question is, are there any other wierd flash bugs that we need to be aware of as programmers, so we don't spend 12 hours debugging something with logic?

I don't know as the things you mentioned before are bugs, but here's something that will make you tear your hair out:

Putting sound files on a timeline in a nested movieclip. Just... just don't. Ever. Not if you're using AS3, at least. Having looked at the specifications for how swf files play, I no longer consider the weirdness that can happen with this a 'bug' as such. Rather, I consider it to be a horrifying side-effect of their intended VM structure that really needs a rethink if it is expected to work in any way that makes logical sense to a user of the authoring tool, but probably won't ever get one because it's so deeply entrenched in the Flash Player architecture that they'd have to scrap any and all semblance of backwards compatibility to fix it.

Sometimes, Flash might just decide to spasm around and screw up. And by sometimes I mean pretty often, seriously.

Like once, I was doing an animation when all of a sudden, it stopped working. All I did was to go to the library and delete all my unused symbols, and viola! The entire animation started playing again, courtesy of Adobe Flash.

[senocular]

browse bugs.adobe.com for Flash Player bugs or log new ones if you find issues that aren't already there.

Originally Posted by senocular

browse bugs.adobe.com for Flash Player bugs or log new ones if you find issues that aren't already there.

Some of those issues are really hard to define, so its a bit pointless reporting it. For example, I added a movie clip on stage when the whole swf screwed up. It really doesn't tell anything, its not like it happens every time you add a MC, its just a random occurence.

Maybe I should switch to back to Windows Vista or XP. Windows 7 beta is bugged to hell.

[senocular]

If there's a problem, it might be worth tracking down the cause so it can be fixed and won't happen again. Even if you can't target the specific cause, if you have a reproducible case, that can usually be good enough.
; )

[grilldor]

Originally Posted by Kimchee

for example, you cant put stage.length or stage.width to get x, y values at the start of a program because the stage's width and length change as the program loads.

Hum, what happened to stage.stageHeight and stage.stageWidth ?

[tg]

Originally Posted by kkbbcute

Maybe I should switch to back to Windows Vista or XP. Windows 7 beta is bugged to hell.

>.<

dont expect stuff to work correctly in a windows beta.

[Flash Gordon]

Originally Posted by tg

>.<

dont expect stuff to work correctly in a windows beta.

don't expect stuff to work correctly in windows