Can you post a small test case?
________________________________ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of j_lentzz Sent: Tuesday, November 06, 2007 3:41 PM To: [email protected] Subject: [flexcoders] Re: Bouncing Focus in DataGrid It happens also when I first populate the datagrid or add a row. In either case, nothing is selected in the datagrid. When I select something, the top most left cell briefly gets the focus and switches the component to an editor then back to a renderer and then the selected item becomes an editor. John --- In [email protected] <mailto:flexcoders%40yahoogroups.com> , George <[EMAIL PROTECTED]> wrote: > > When you add a new row, dataProvider changed so DG will be refreshed > totally, your item editing process will be eliminated at that time. > You need a callLater() to reselect .selectedIndex to the new row, it > will be highlighted. Then try to move focus back to the renderer. > > George > > Alex Harui wrote: > > Are the renderers also editors? rendererIsEditor="true". If so, is the > > renderer an IFocusManagerComponent? > > ________________________________ > > > > From: [email protected] <mailto:flexcoders%40yahoogroups.com> [mailto:[email protected] <mailto:flexcoders%40yahoogroups.com> ] On > > Behalf Of j_lentzz > > Sent: Tuesday, November 06, 2007 6:06 AM > > To: [email protected] <mailto:flexcoders%40yahoogroups.com> > > Subject: [flexcoders] Bouncing Focus in DataGrid > > > > Hello All, > > > > I have an app that allows the user to add rows to a datagrid. The > > rows contain components that have separate item editors and renderers. > > What is happening is that after a new row is added to the datagrid > > and the user clicks on a cell that is not the first cell in the first > > row, the focus briefly goes to the first cell in the first row and > > then to the actual cell selected. It doesn't stay there long, but > > long enough to see the cell switch to the item editor and then back to > > the renderer. Has anyone else seen this or have a way to prevent it? > > > > Thanks, > > > > John > > >
