Thanks everyone for your help and ideas. Very useful. I have something
working now, but not with a custom component, though Jim I will try out
your ideas there.
My next architecture question has to do with states and navigation. I
have a TabBar I am trying to use to navigate between different states -
different pages in my application which all look very different except
the navigation piece. Is this the best way to handle switching between
different screens? I was able to render the TabBar based on my data
bindings without a problem, and I can register the event that the tab
was clicked, but i was unable to get it to change states. I tried:
private function tabClick(event:ItemClickEvent):void {
var targetComp:TabBar = TabBar(event.currentTarget);
forClick.text="label is: " + event.label + " index is: " +
event.index + " capital is: " +
targetComp.dataProvider[event.index].data;
currentState = targetComp.dataProvider[event.index].data;
}
Where .data is the name of the state I want to change to. What is the
proper approach? Thanks!
Jason Merrill
Bank of America
Learning & Organizational Effectiveness
