Issue 5 - flexlib - Sorting TreeGrid causes erroneous results

Issue 5:	Sorting TreeGrid causes erroneous results	‹ Prev 2 of 199 Next ›
	6 people starred this issue and may be notified of changes.	Back to list

Status:	Accepted
Owner:	darron.schall
Type-Defect
Priority-Medium
FlexLib-TreeGrid

Reported by darron.schall, Mar 20, 2007

What steps will reproduce the problem?
1. Open
http://flexlib.googlecode.com/svn/trunk/examples/TreeGrid/TreeGrid_Sample.swf
2. Expand Macromedia and Sector 02 on the left
3. Click the name header to sort, notice how the hierarchy is broken at
this point
4. Click Sector 02 to close it, and notice the run-time error

RangeError: Index '8' specified is out of bounds.
	at mx.collections::ListCollectionView/removeItemAt()
	at flexlib.controls::TreeGrid/closeItemAt()
	at flexlib.controls::TreeGrid/dispatchTreeEvent()
	at
flexlib.controls.treeGridClasses::TreeGridItemRenderer/::disclosureMouseDownHandler()

What is the expected output? What do you see instead?

I'm not 100% sure what the expected output should be.  My best guess would
be that the names at each "level" of the heirarchy would be sorted in
alphabetical order, but that the overall structure of the hierarchy remains
the same.  In this example, after sorting with Macromedia and Sector 02
open, I think the order should be:

Adobe
Macromedia
  Sector 01
  Sector 02
    Class 01
    Class 02
  Sector 03
Microsoft
Oracle

Comment 1 by yderidde, Mar 24, 2007

this is a feature i need to implemen, i would like the sorting feature to work, the
current Flex Tree dont support that and therefor i think it can be useful :)

for the expected result, that right each level will be sorted independently.

Comment 2 by darron.schall, Apr 05, 2007

(No comment was entered for this change.)

Labels: TreeGrid

Comment 3 by dmccune, Dec 26, 2007

(No comment was entered for this change.)

Labels: -TreeGrid FlexLib-TreeGrid

Comment 4 by siddharth.balaravi, Mar 14, 2008

I downloaded v2.4 of the flexlib...and still noticed this issue...are there any plans
on fixing this in the near future?