|
Thanks for your reply. The tabbar isn’t
actually attached to a viewstate or anything, it basically is used to send service requests
which update a datagrid. I’ve tried creationcomplete
on the actual tabbar, no joy. The selectedIndex
of the tabbar IS set right, but the button just doesn’t
get selected. -----Original Message----- Creationcomplete of what component? Are you aware that the navigator
components all use deferred instantiation by default, and the child components
do not exist until a user first navigates to the view? If you think this might be the
issue, you can, for testing purposes only ( Gordon ;) ), set
creationPolicy=”all” on the nav containers. If that fixes the
problem, search the archives for the thread titled “Why you shouldn't set
creationPolicy="all" to solve your deferred instantiation
problems”. Seriously. From:
[email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Steve Cox Guys + Girls, I’ve a tabbar on 3 separate
forms inside a Tab Nav. Now the dataprovider for these is
populated from a webservice, the issue I’m having is setting the
selectedIndex on the tabbars initially. Once the tabbar is created, the
selectedindex works perfect. Setting the selectedindex in a
creationcomplete event doesn’t work, is there an event which is fired to
notify when a tabbar has built up it’s buttons? I’ve tried
childrenCreated but I suspect that’s for when it’s attached to a
viewstate etc. Stupid problem I know, but it’s always the little ones
that cause the most problems! Cheers, Steve
|
