Hi,
> Is a 1009 always a null ref? I never tried to memorize that, I always read
> the full message.
I guess it's possible (but very unlikely IMO) for the Flash Player to use the
same error number for two different errors. It's certainly not documented.
http://help.adobe.com/en_US/FlashPlatform
On 2/4/13 2:34 PM, "Justin Mclean" wrote:
> Hi,
>
>> Maybe there is a problem with my email, but I do not see the "Cannot..." in
>> your original email
> The full error message is not reported by the Flash Player in the stack
> trace, but the error number 1009.
Is a 1009 always a null ref?
Hi,
> Maybe there is a problem with my email, but I do not see the "Cannot..." in
> your original email
The full error message is not reported by the Flash Player in the stack trace,
but the error number 1009.
> It was, but then it seemed like you were suggesting something more
> complicated.
I
On 2/4/13 12:58 AM, "Justin Mclean" wrote:
> Hi,
>
>> I didn't think that resulted in a TypeError. I thought it was some other
>> error.
> TypeError: Error #1009: Cannot access a property or method of a null object
> reference.
Maybe there is a problem with my email, but I do not see the "Ca
Hi Max,
Thanks for the links good to know i'm not the only person who's run into it and
hopefully we can come up with a fix.
Justin
I was certain I had seen this somewhere before and after poking my brain
with a stick for a little while I remembered that someone had asked a
question about this exact issue on StackOverflow:
http://stackoverflow.com/questions/13847817/upgrading-from-flex-3-0-to-flex-3-6-custom-combobox-getting-ty
Hi,
> I didn't think that resulted in a TypeError. I thought it was some other
> error.
TypeError: Error #1009: Cannot access a property or method of a null object
reference.
Can't get much clearer than that :-)
> Or just add a null check there.
Thought that what I suggested?
Thanks,
Justin
On 2/3/13 10:41 PM, "Justin Mclean" wrote:
> Hi,
>
>> Seems like an impossible situation.
> Why do you think that? Tween could be null and that would cause a RTE.
I didn't think that resulted in a TypeError. I thought it was some other
error.
>
> Looking at rest of code inTween is not set/u
Hi,
> Seems like an impossible situation.
Why do you think that? Tween could be null and that would cause a RTE.
Looking at rest of code inTween is not set/unset at the same time when tween is
created so it's a possibility. In fact I can't see where it set to null at all
other than initially s
Seems like an impossible situation. I don't really see an opportunity for a
TypeError in ComboBox's destroyDropDown. I winder if the 11.5 stack doesn't
report everything on the stack.
On 2/3/13 6:38 PM, "Justin Mclean" wrote:
> Hi,
>
> Wondering if anyone run into this error. I been unable
10 matches
Mail list logo
