On Mon, Jan 5, 2009 at 10:01 PM, endrone endrone <[email protected]> wrote: > currentStateChange and enterState don't work with a TabNavigator > They are indeed in the docs, but they don't seem to work.
Are you using the states feature at all? A TabNavigator by itself won't dispatch these events, unless you're assigning different states to it. > creationComplete and initialize only happen once. Only once per container here. Each tab in the TabNavigator will dispatch its own initialize event, where you can initialize it. > With states you can easily init a state with the enterState event. > I want something similar for the TabNavigator. > Now I listen for the Change event of the TabNavigator and keep the prevIndex > in a variable. > And depending on the index I initialize the TabView. > Is that a best practice? It's either the TabNavigator's 'change' (your current method) or its children's 'initialize'. It's hard to say without knowing more about the sort of initialization you're doing here. Manish
