Module + Tab Navigator = Error

Question

Everything works FINE until I load a new module. (Even after
I go back to the original module, I get the error). Any component
with a Tab Container or Accordian throws the following error when I
load the component:
TypeError: Error #1009: Cannot access a property or method of
a null object reference.
at mx.managers::HistoryManager$/register()
at mx.containers::ViewStack/::addedHandler()
at flash.display::DisplayObjectContainer/addChildAt()
at mx.core::UIComponent/
http://www.adobe.com/2006/flex/mx/internal::$addChildAt()
at mx.core::Container/addChildAt()
at mx.core::Container/addChild()
at mx.core::Container/createComponentFromDescriptor()
at mx.core::Container/createComponentsFromDescriptors()
at mx.core::Container/mx.core:Container::createChildren()
at mx.core::UIComponent/initialize()
I have turned off History manager in the compiler page of the
project properties. That does not help any.
Any suggestions?
Thanks
Bruce

Answer 1

Hi Bill,
> Found a problem when submitting a textinput field from a
canvas on a
> TabNavigator. Problem only occurs when you do not go to
the tab when viewing
> on screen before submitting the TextInput.text
>
> This is the error.
> TypeError: Error #1009: Cannot access a property or
method of a null object
> reference.
>
> If you click on the tab, view the contents of whatever
and then submit, there
> is no error. If you do NOT click on the tab, then the
error occurs. Seems
> like it does not create the tab until you view it. Which
would not seem
> correct. Think of the case of entry screens where you
have 3 or 4 or more tab
> sections on the screen.
Try setting creationPolicy="all" on the TabNavigator. By
default,
creationPolicy is set to "auto", which means the TabNavigator
only
creates the children of the initially visible pane on
startup--this is
to make startup faster. In your case, since you need to
access children
of the hidden tabs regardless of whether the user visits
them, you
should use creationPolicy="all".
nj
Flex Builder team