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.
Until there is at least one selection.
..and also automatically select just added one ui/customizer/CustomizerLibraries.java; 1.46 -> 1.47;
Really do not know why (probably lack of my UI knowledge), but sometime JList.getMinSelectionIndex() (delegate to selection model) returns value > JList.getModel().getSize() which causes AIOOBE in our custom model. I'll have to add sanity check into getElementAt into our model. If anybody know what's going on, let me know.
So should be ok now. ui/customizer/CustomizerComponentFactory.java; 1.10 -> 1.11; ui/customizer/CustomizerLibraries.java; 1.47 -> 1.48;
Backported. ui/customizer/CustomizerComponentFactory.java; 1.9.2.1 -> 1.9.2.2; ui/customizer/CustomizerLibraries.java; 1.44.2.2 -> 1.44.2.3;
Re. JList behavior - sounds like a Swing bug to me, so if you can reproduce in a standalone case that would be a good bug report I think?
I'll put it on my todo list. Do not believe too much to JDK bug, though did not find anything strange in our implementation. Seems to me like some data are shared between two selection models inappropriately since one instance of selection model returns actually its minSelectionIndex equals to selection index of other one. Or maybe selection model itself is somehow reused. Also those two lists models has the same elements shared (Strings). Hmm, litle confused. I'll have to investigate more.