Ahh, now I understand why I wrote about creationPolicy. I still messed up that email though, haha.
Alex said it in his email: >Way early in this thread I mentioned that, depending on your creationPolicy, >objects on yet-to-be-viewed tabs may not exist or have invalid sizes. The problem in your case is that you are dealing with a visual component. This component will not be completed until you move to that tab. In a previous post, you said that setting creationPolicy on the parent container would not help as well. If you have the datagrid in a tab navigator component i asume that the datagrid is in somesort of container. I asume this because the tab navigator requires containers as children. The tab navigator however has creationPolicy set to 'auto', which means it will create it's immediate children, but not the datagrid. Setting creationPolicy on the tab navigator to 'all' should help in your case. If it does not, you are most likely dealing with a timing issue. If you still can not get it to work, could you please make a simplified example of your problem and mail it to me? I could then take a look. Greetz Erik On 5/22/08, aceoohay <[EMAIL PROTECTED]> wrote: > > Erik: > > It does not seem to be a timing issue per se, in other words if I > wait 5 minutes after the dataprovider has been set, it makes no > difference. The only thing that seems to make a difference is > actually viewing the grid by clicking on the tab that the grid is on. > > Paul >
