[ 
https://issues.apache.org/jira/browse/FLEX-34060?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13888641#comment-13888641
 ] 

Alex Harui commented on FLEX-34060:
-----------------------------------

IMO, the issue is that you are trying to resize the row as the editor appears.  
I don't think the DG was designed to handle that.

So, solutions to try probably involve resizing the row before starting the edit 
session.  There are events like ITEM_EDIT_BEGINNING that can be used to cancel 
the start of an edit session, then you can try resizing the row, scrolling to 
the new bottom, and then starting the edit session by setting 
editedItemPosition (and setting some flag so you don't cancel it in your 
ITEM_EDIT_BEGINNING handler.  Another possibility is to try adding a fake blank 
row so the editor never has to appear on the last row.

HTH,
-Alex

> Datagrid not scrolling completely incase of variable row height used with 
> renderer as editor
> --------------------------------------------------------------------------------------------
>
>                 Key: FLEX-34060
>                 URL: https://issues.apache.org/jira/browse/FLEX-34060
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: mx: DataGrid, MXItemRenderer, Spark: TextArea
>    Affects Versions: Apache Flex 4.10.0
>         Environment: Apache Flex 4,Windows 7
>            Reporter: Mitesh Dave
>            Priority: Critical
>         Attachments: RendererEditor.fxp, State 1.png, problem state.png
>
>   Original Estimate: 96h
>  Remaining Estimate: 96h
>
>  I need help in flex datagrid bug. I have a MX datagrid which has renderer as 
> editors and variable row height.
> My renderers have textarea which shows up  whenever they receive focus ,The 
> problem is whenever user is at bottom rows and if renderers receive focus.The 
> datagrid doesnt scroll completely and the rows get clipped.
>  Please find attached screen shot .
> Please help me to get a possible solution for this.i also have attached a 
> sample code to demonstrate the issue and recieve possible solutions.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Reply via email to