TypeError: Error #1009
Chances are that you've seen this error message before. This is my number one wish for ALL the Adobe compilers - better error messages! I've always wondered why Flash / Flex can't throw proper error messages and this is a brilliant example. In this case, Flash obviously knows exactly what is wrong so why not just just tell it? How about something like this:
TypeError: Error #1009: Cannot access the property "someprop" since it is a null object reference.
at no.netron.tusenfryd::Map/onLoadSingle()
at flash.events::EventDispatcher/dispatchEventFunction()
at flash.events::EventDispatcher/dispatchEvent()
at flash.net::URLLoader/onComplete()
If I just knew the name of the object, I didn't have to search all over for it...
Comments
amen.
Posted by: Keith Peters | February 22, 2008 02:16 PM
I don't get it. If you are debugging using Flex builder the line with the error will be highlighted. If you are using a debug player it will give you the exact line number of the error.
This should be enough.
Another thing is that they (in most cases) can not give you the name of the property. In swf files all the local function properties are nameless. If you would decompile an swf your would see them named as local1 to localX.
Greetz Erik
Posted by: Erik Westra | February 23, 2008 12:13 PM
Hi Erik,
I'm not using Flex. For this project I work with designers and need movieclips and the timeline for them to do their stuff.
But - what you say about variables being renamed is true. They should be able to solve this when you are running inside the IDE though, don't you think?
And really, this is just one out of hundreds. Many of them are not really informative at all. I'm sure they could have done better without putting too much effort into it.
Posted by: Jensa | February 24, 2008 12:32 PM
cambiamos la pec de gravacion
aprentemente isimos todos los pasos de ciempre aparece error
1009 chek hardlock emos ejecutado hardlock pero no cambia
Posted by: Jorje Wenlinger | February 26, 2008 06:42 PM