This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
The elements are listed in the order 0, 10..19, 1, 20 etc, as if they are sorted as text.
Just noticed its been fixed in 4.1.
Back in 200503281924.
Fixed in current build.
Not fixed in 200504101930.
No chance to fix it in 4.1.
What does "No chance" mean? Won't we get a chance to vote before it is waived?
P3 issue is not subject to be waived.
*** Issue 63108 has been marked as a duplicate of this issue. ***
It's impossible to fix unless we change the display name. There is just "n1.getDisplayName().compareTo(n2.getDisplayName())" comparison hard-coded in TreeTableView.SortedNodeTreeModel. I'll request an enhancement in openide so that we'll be able to supply a Comparable.
The numbers are prepended with spaces. This fixes the sorting: /cvs/debuggerjpda/src/org/netbeans/modules/debugger/jpda/models/AbstractVariable.java,v <-- AbstractVariable.java new revision: 1.33; previous revision: 1.32 /cvs/debuggerjpda/src/org/netbeans/modules/debugger/jpda/models/ArrayFieldVariable.java,v <-- ArrayFieldVariable.java new revision: 1.7; previous revision: 1.6 /cvs/debuggerjpda/src/org/netbeans/modules/debugger/jpda/models/LocalsTreeModel.java,v <-- LocalsTreeModel.java new revision: 1.32; previous revision: 1.31 /cvs/debuggerjpda/src/org/netbeans/modules/debugger/jpda/models/ObjectArrayFieldVariable.java,v <-- ObjectArrayFieldVariable.java new revision: 1.6; previous revision: 1.5
You might be able to use U+200C ZERO WIDTH NON-JOINER or U+200B ZERO WIDTH SPACE to avoid affecting appearance - unless the Node.displayName sorting is done with a natural-language Collator (rather than String.compareTo) and these are ignored by it.
Unfortunately both U+200C ZERO WIDTH NON-JOINER and U+200B ZERO WIDTH SPACE are "bigger" than any digit in String.compareTo(). :-(
Tested with build 200510171800.