You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flex.apache.org by "Andreas Niekler (JIRA)" <ji...@apache.org> on 2013/05/28 09:58:22 UTC

[jira] [Created] (FLEX-33577) scrollToIndex produces errors if the index to scroll to is not visible in AdvancedDataGrid

Andreas Niekler created FLEX-33577:
--------------------------------------

             Summary: scrollToIndex produces errors if the index to scroll to is not visible in AdvancedDataGrid
                 Key: FLEX-33577
                 URL: https://issues.apache.org/jira/browse/FLEX-33577
             Project: Apache Flex
          Issue Type: Bug
          Components: Advanced Data Grid
    Affects Versions: Apache Flex 4.9.0
         Environment: FlashBuilder 4.6
            Reporter: Andreas Niekler


Hello,

i created a custom column ADG where i import new data via BlazeDS. Normally the backing list contains 50 elements. All those Elements represent a dataset which i can load into a data view and than do some edits. For a better workflow i added a "done, save & next" button which changes the selected index to the next element of the ADG and loads it. To follow the selected item in the ADG i implemented the scrollToIndex function within that process. Now the behavior:

The scrollToIndex function does nothing while the slected indexes are in the visible part of the ADG. Once i reach an index of an element that is not visible yet the selectedIndex = selectedIndex + 1 produces the MinInteger Value because this next element isn't rendered yet. I made a workaround by forwarding the verticalScrolling by 1 element to surly render the next element but the scrollToIndex function produces massive errors (FlashPlayer produces 4GB memory usage and crashes the OS, shows exclamation mark error) when using it with that invalid index. 

Is there a solution to render the next n elements in advance or to deactivate lazy rendering in ADG's.  

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira