[ 
https://issues.apache.org/jira/browse/FLEX-35280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mihai Chira updated FLEX-35280:
-------------------------------
    Description: 
{{GridColumnHeaderGroup.getHeaderIndexAt() -> 
GridHeaderViewLayout.getHeaderIndexAt() -> 
GridDimensionsView.getColumnIndexAt() -> GridDimensions.getColumnIndexAt()}}. 
In the last step of this chain of function calls the y argument is simply 
ignored, resulting in erroneous results.

Note that it looks like the initial intention of the developers was not to 
ignore the y argument. The function description supports this: ??Returns the 
index of the column at the specified coordinates. If the coordinates lie in a 
gap area, the index returned is the previous column. Returns -1 if the 
coordinates are out of bounds.??

  was:
{{GridColumnHeaderGroup.getHeaderIndexAt() -> 
GridHeaderViewLayout.getHeaderIndexAt() -> 
GridDimensionsView.getColumnIndexAt() -> GridDimensions.getColumnIndexAt()}}. 
In the last step of this chain of function calls the y argument is simply 
ignored, resulting in erroneous 

Note that it looks like the initial intention of the developers was not to 
ignore the y argument. The function description supports this: ??Returns the 
index of the column at the specified coordinates. If the coordinates lie in a 
gap area, the index returned is the previous column. Returns -1 if the 
coordinates are out of bounds.??


> Spark DataGrid getColumnIndexAt ignores y value when returning column index
> ---------------------------------------------------------------------------
>
>                 Key: FLEX-35280
>                 URL: https://issues.apache.org/jira/browse/FLEX-35280
>             Project: Apache Flex
>          Issue Type: Bug
>          Components: Spark: DataGrid
>    Affects Versions: Apache Flex 4.14.1
>            Reporter: Mihai Chira
>            Assignee: Mihai Chira
>             Fix For: Apache Flex 4.15.0
>
>
> {{GridColumnHeaderGroup.getHeaderIndexAt() -> 
> GridHeaderViewLayout.getHeaderIndexAt() -> 
> GridDimensionsView.getColumnIndexAt() -> GridDimensions.getColumnIndexAt()}}. 
> In the last step of this chain of function calls the y argument is simply 
> ignored, resulting in erroneous results.
> Note that it looks like the initial intention of the developers was not to 
> ignore the y argument. The function description supports this: ??Returns the 
> index of the column at the specified coordinates. If the coordinates lie in a 
> gap area, the index returned is the previous column. Returns -1 if the 
> coordinates are out of bounds.??



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to