You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flex.apache.org by "Mihai Chira (JIRA)" <ji...@apache.org> on 2017/04/12 11:33:41 UTC

[jira] [Updated] (FLEX-35280) Spark DataGrid getHeaderIndexAt() and getColumnIndexAt ignore y value when returning column index

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

Mihai Chira updated FLEX-35280:
-------------------------------
    Summary: Spark DataGrid getHeaderIndexAt() and getColumnIndexAt ignore y value when returning column index  (was: Spark DataGrid getColumnIndexAt ignores y value when returning column index)

> Spark DataGrid getHeaderIndexAt() and getColumnIndexAt ignore 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, creating 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)