No, not a bug. Containers in Flex 2 use differed instantiation by default.
That is, children are not created until they need to be shown, which is why
your DataGrid doesn't exist until the user clicks on its tab. A simple
solution is to set the TabNavigator's creationPolicy="all" to force it to
create all its children at the beginning (but this could potentially
increase startup time).
On 3/24/06, Fredrik Sandberg <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
>
>
> I have some serious problems refreshing content in a Flex2 beta2 datagrid,
> located inside a tabnavigator.
>
> The content consists of mailheaders, and the grid could (of course)
> contain
> 0-many mails.
>
> The data is captured from a DB, via HTTPService. The datagrid is loaded
> with:
>
>
>
> try {
>
> uMailGrid.dataProvider = arrUMails;
>
> } catch (e:Error) {
>
> uMailGrid.data = arrUMails;
>
> }
>
>
>
> Is there a better way to do this?
>
> And for my major concern: why doesn´t the datagrid refresh???
> uMailGrid.freeItem doesn´t has no effect.
>
>
>
> It seems like the user have to click through the tabs in order to have the
> items "activated" / properly drawn.
>
> There must b something buggy about this, or?
>
>
>
> Thanks,
>
> Fredrik Sandberg
>
>
>
> _______________________________________________
> [email protected]
> To change your subscription options or search the archive:
> http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
>
> Brought to you by Fig Leaf Software
> Premier Authorized Adobe Consulting and Training
> http://www.figleaf.com
> http://training.figleaf.com
>
_______________________________________________
[email protected]
To change your subscription options or search the archive:
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
Brought to you by Fig Leaf Software
Premier Authorized Adobe Consulting and Training
http://www.figleaf.com
http://training.figleaf.com
