Hey, now there's a good idea. Why haven't I thought of that before? (written in a non-sarcastic manner)
On Tue, Sep 9, 2008 at 10:14 AM, Alex Harui <[EMAIL PROTECTED]> wrote: > Use a debug build so you get line numbers and post the entire > stacktrace if it isn't clear where the problem is. > > > > *From:* flexcoders@yahoogroups.com [mailto:[EMAIL PROTECTED] *On > Behalf Of *scowling_beer > *Sent:* Monday, September 08, 2008 11:38 PM > *To:* flexcoders@yahoogroups.com > *Subject:* [flexcoders] Error #1009: Property or Mehtod of a null object > reference > > > > Hello All, > > Firstly I understand what causes the #1009 error. > > What I am having trouble with is reproducing it in my flex development > environment. > > I have an application that calls custom components into a ViewStack. > When the user changes sections within the viewstack it fires an event which > calls a public method called saveSection *within *the custom component - > the section they just left. > > When debugged and run within my Flex dev environment it works fine, *until > * I deploy it to *another *development machine. It's then that I get the > Error 1009. > > This is driving me crazy. This code has previously worked fine. > > I'm happy to post some pseudo code or examples if needed, but generally I'm > after advice. If I am viewing the component called into the viewstack... how > can it be null? Complicating this is that the *same* code called for the > other sections works as expected! > > The creationPolicy on the viewstack is "all" > > MainApp > {changeSectionHandler -> oldSection.saveSection()} > ViewStack > SectionA > {saveSection()} > SectionB > {saveSection()} > SectionC > {saveSection()} > > Any help appreciated. > > Cheers > Steve > > >
