Skip navigation
eprevot123
eprevot123
Currently Being Moderated

stuck in ListBase.setSelectionDataLoop

Mar 18, 2011 2:21 AM

Sometimes when I set the selectedItem of a Tree after changing its dataprovider, the application freezes :

when I debug and look at the collectionIterator of the Tree, it still has information of the old dataprovider, and the ListBase.setSelectionDataLoop enters an infinite loop.

 

I tried to set the selectedItem in a callLater, and call :

tree.invalidateList();
tree.invalidateSize();
tree.invalidateDisplayList();
tree.validateNow();

 

and it works in most of the cases, but in some cases my application still freezes.

 

Do you know how can I be sure to update my Tree before I set the selectedItem ?

1147 Views   9 Replies   Latest reply: kkudiksx, Jan 11, 2012 7:09 AM
 
Replies
  • eprevot123
    Currently Being Moderated
    1. eprevot123,
    Mar 18, 2011 7:40 AM   in reply to eprevot123
    Report

    It seems I validated everything but what is needed : the properties.

     

    To make it work, I replaced :

    tree.invalidateList();
    tree.invalidateSize();
    tree.invalidateDisplayList();
    tree.validateNow();

     

    with:

    tree.validateProperties();

     

    When I was stucked in an infinite loop in setSelectionDataLoop, I noticed the dataProviderChanged flag was true. If I validate the properties before I set the selectedItem then it works fine.

     
    |
    Mark as:
  • eugene_se
    Currently Being Moderated
    2. eugene_se,
    Oct 16, 2011 12:13 AM   in reply to eprevot123
    Report

    Thanks, you saved my day!

     
    |
    Mark as:
  • Wim Deblauwe
    Currently Being Moderated
    3. Wim Deblauwe,
    Dec 15, 2011 8:49 AM   in reply to eprevot123
    Report

    Thanks for this, I have the same problem. Hopefully this workaround fixes it.

     
    |
    Mark as:
  • kkudiksx
    Currently Being Moderated
    4. kkudiksx,
    Jan 11, 2012 6:09 AM   in reply to eprevot123
    Report

    I have the exact same problem but tree.validateProperties() has not fixed the problem!

     
    |
    Mark as:
  • Wim Deblauwe
    Currently Being Moderated
    5. Wim Deblauwe,
    Jan 11, 2012 6:20 AM   in reply to kkudiksx
    Report

    Indeed, for me neither. What I then did was use selectedIndex instead of selectedItem and that seemed to help.

     
    |
    Mark as:
  • kkudiksx
    Currently Being Moderated
    6. kkudiksx,
    Jan 11, 2012 6:35 AM   in reply to eprevot123
    Report

    hm I ll give it a go and let you know!

     
    |
    Mark as:
  • kkudiksx
    Currently Being Moderated
    7. kkudiksx,
    Jan 11, 2012 6:50 AM   in reply to eprevot123
    Report

    selectedIndex worked for me! Thank you so much Wim!

     
    |
    Mark as:
  • eprevot123
    Currently Being Moderated
    8. eprevot123,
    Jan 11, 2012 7:01 AM   in reply to kkudiksx
    Report

    If selectedItem did not work, it may remain an inconsistence between the dataProvider and what is displayed :

    If you use selectedIndex you may have a wrong behaviour, for example :

    you add an item to the dataProvider, and set selectedIndex to "dataProvider.length -1" but the view is not ready for the new dataprovider and does not know any item at this index.

     
    |
    Mark as:
  • kkudiksx
    Currently Being Moderated
    9. kkudiksx,
    Jan 11, 2012 7:09 AM   in reply to eprevot123
    Report

    I'm using callLater so I don't think I will have any inconsistencies. I may be wrong though.

     

    In Flex 3.2 selectedItem = item worked. So it might be a Flex 3.* where * > 2 or a Flex 4 bug.

     
    |
    Mark as:
Actions

More Like This

  • Retrieving data ...

Incoming Links

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points